-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm start failed (code: 'ERR_PACKAGE_PATH_NOT_EXPORTED') #11579
Comments
Can be temporarely fixed by downgrading to 16.13.0 |
for anyone on mac needing the above temp fix which worked for me. |
The "temp fix" is now two weeks old, any better fix out there yet? |
hello,
hope this will help waiting for the fix. |
cmd > npm i node@16. Now I can launch node@17. Looks like something missing in a clean node@17 |
fixed the bug for me, and React App started working. |
"yarn upgrade" fixed the bug for me, and everything works perfectly. |
why is this error being thrown though, is it because of dependencies incompatibility ?? |
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. |
If you got a message saying you will no longer receive security fixes if you do not upgrade when running |
Looking to learn react so, basically upgraded my nodejs and npm and went for an That is:
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 Lucked into this bug report. Ran So, steps:
What fixed it for me was remover nodejs 17.2.0 and install 16.13.1 thanks. |
This worked for me on
|
but, need to yarn upgrade every time |
Fixed by running |
Awesome! That was easy fix, THANKS TO YOU! |
"start": "react-scripts --openssl-legacy-provider start", That worked for me |
"start": "react-scripts --openssl-legacy-provider start", that worked for me x2 |
OpenSourceHelpCommunity/Questions#337 |
Error:
[1] ''react-scripts' is not recognized as an internal or external command, package.json content
|
Install 'react-scripts I always think it’s bad to have it |
its install npm ls -g react-scripts PS C:\Users\AchalBhangreNational\IdeaProjects\nbi-spport-ui> npm ls react-scripts node -v
|
➜ my-app git:(master) npm 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
The text was updated successfully, but these errors were encountered: