npm start failed （code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'）

[zzz6519003]

➜ my-app git:(master) npm start

[email protected] start
react-scripts start

node:internal/modules/cjs/loader:488
throw e;
^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in /Users/zzz/Develop/my-app/node_modules/postcss-safe-parser/node_modules/postcss/package.json
at new NodeError (node:internal/errors:371:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:416:9)
at packageExportsResolve (node:internal/modules/esm/resolve:669:3)
at resolveExports (node:internal/modules/cjs/loader:482:36)
at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:999:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/Users/zzz/Develop/my-app/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v17.0.1

[Yochyo]

Can be temporarely fixed by downgrading to 16.13.0

[AnthonyPoschen]

for anyone on mac needing the above temp fix which worked for me.
brew install node@16

[Ueland]

The "temp fix" is now two weeks old, any better fix out there yet?

[Lionprincipe]

hello,
I 'am using Node.js v17.0.1 and upgrading my package helped me solved this issue without downgrading the node version.

"yarn upgrade"

hope this will help waiting for the fix.

[rainyEra]

cmd > npm i node@16. Now I can launch node@17. Looks like something missing in a clean node@17

[Ansub]

"yarn upgrade"

fixed the bug for me, and React App started working.

[aeskafi]

"yarn upgrade"

fixed the bug for me, and everything works perfectly.

[kedbirhan]

why is this error being thrown though, is it because of dependencies incompatibility ??

[Ansub]

yeah, I think when we install react, it installs on the latest version, but the yarn was not updated to that version that supports the version of react. "yarn upgrade" fixed the bug because it upgrades packages to their latest version.

[nlintas]

If you got a message saying you will no longer receive security fixes if you do not upgrade when running yarn start or npm start then the solution is to run yarn upgrade, this will update the yarn packages and resolve this issue.

[Bazmundi]

Looking to learn react so, basically upgraded my nodejs and npm and went for an npx create-react-app following the destructions at: https://reactjs.org/docs/create-a-new-react-app.html

That is:

npx create-react-app my-app
cd my-app
npm start

Running on Windows 10, Node.js v17.2.0, npm/npx comes up as 8.2.0.

As I had not previously installed react, the npx command line above kindly pulled that in.

So, changed directory into my-app thence npm start left the insult at: https://pastebin.com/czGkpX1K

Lucked into this bug report. Ran yarn update thanks. Changes the insult to the following insult: https://pastebin.com/Zdchie2b

So, steps:

• Run npm create-react-app from install that only has nodejs and npm/npx (no react but react gets pulled in)
• Run app get https://pastebin.com/czGkpX1K
• Run yarn update then run either of npm start or yarn start get https://pastebin.com/Zdchie2b
• Delete folder, re-run npm create-react-app and run app to get https://pastebin.com/czGkpX1K

What fixed it for me was remover nodejs 17.2.0 and install 16.13.1 thanks.

[YousefAlsbaihi]

yarn upgrade

This worked for me on

"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-scripts": "4.0.3",

[zzz6519003]

but, need to yarn upgrade every time

[jhkcia]

Fixed by running npm upgrade

[ananshe]

cmd > npm i node@16. Now I can launch node@17. Looks like something missing in a clean node@17

Awesome! That was easy fix, THANKS TO YOU!

[timothymureithi]

"start": "react-scripts --openssl-legacy-provider start",
"build": "react-scripts --openssl-legacy-provider build"

That worked for me

[xtRAVEN]

"start": "react-scripts --openssl-legacy-provider start",
"build": "react-scripts --openssl-legacy-provider build"

that worked for me x2
thanks @timothymureithi

[HeyKalangi]

OpenSourceHelpCommunity/Questions#337
needed some help..

[Achal9099]

Error:
npm start

[email protected] start
npm run build:css && concurrently --kill-others 'npm:watch:css' 'react-scripts --openssl-legacy-provider start'

[email protected] build:css
postcss src/app/shared/styles/tailwind.css -o src/app/shared/styles/main.css

[1] ''react-scripts' is not recognized as an internal or external command,
[1] operable program or batch file.
[1] 'react-scripts exited with code 1
--> Sending SIGTERM to other processes..
[watch:css] npm run watch:css exited with code 1

package.json content
"scripts": {
"start": "npm run build:css && concurrently --kill-others 'npm:watch:css' 'react-scripts --openssl-legacy-provider start'",
"build": "npm run build:css && react-scripts --openssl-legacy-provider build",
"build:js": "react-scripts --openssl-legacy-provider build",
"test": "react-scripts test",
"test:all": "react-scripts test --watchAll=false",
"test:coverage": "react-scripts test --coverage --watchAll",
"test:debug": "react-scripts --inspect-brk test --runInBand --no-cache",
"eject": "react-scripts eject",
"prettier:base": "prettier 'src/**/*.{js,jsx,ts,tsx,json,css,scss,md}'",
"prettier:check": "yarn prettier:base --check",
"prettier:fix": "yarn prettier:base --write",
"l

Can someone help?

[zzz6519003]

Install 'react-scripts

I always think it’s bad to have it

[Achal9099]

its install

npm ls -g react-scripts
C:\Program Files\nodejs -> .
`-- [email protected]

PS C:\Users\AchalBhangreNational\IdeaProjects\nbi-spport-ui> npm ls react-scripts
[email protected] C:\Users\AchalBhangreNational\IdeaProjects\nbi-spport-ui
+-- @storybook/[email protected]
| -- [email protected] deduped -- [email protected]

node -v
v18.20.4

npm -v
10.7.0
yarn -v
1.22.22