npm start failed （code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'）

➜ my-app git:(master) npm start

my-app@0.1.0 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

Can be temporarely fixed by downgrading to 16.13.0

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

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

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.

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

"yarn upgrade"

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 yarn start or npm start then the solution is to run yarn upgrade, this will update the yarn packages and resolve this issue.

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.

yarn upgrade

This worked for me on

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

but, need to yarn upgrade every time

Fixed by running npm upgrade

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!

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

That worked for me

@timothymureithi

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

that worked for me x2
thanks @timothymureithi

OpenSourceHelpCommunity/Questions#337
needed some help..

Error:
npm start

nbi-spp-ui@7.12.0-SNAPSHOT start
npm run build:css && concurrently --kill-others 'npm:watch:css' 'react-scripts --openssl-legacy-provider start'

nbi-spp-ui@7.12.0-SNAPSHOT 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?

Install 'react-scripts

I always think it’s bad to have it

its install

npm ls -g react-scripts
C:\Program Files\nodejs -> .
`-- react-scripts@5.0.1

PS C:\Users\AchalBhangreNational\IdeaProjects\nbi-spport-ui> npm ls react-scripts
nbi-spp-ui@7.12.0-SNAPSHOT C:\Users\AchalBhangreNational\IdeaProjects\nbi-spport-ui
+-- @storybook/preset-create-react-app@2.1.2
| -- react-scripts@4.0.1 deduped -- react-scripts@4.0.1

node -v
v18.20.4

npm -v
10.7.0
yarn -v
1.22.22

Navigation Menu

Repository navigation

npm start failed （code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'） #11579

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

npm start failed （code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'） #11579

Description

Activity

Yochyo commented on Oct 29, 2021

AnthonyPoschen commented on Nov 6, 2021

Ueland commented on Nov 11, 2021

Lionprincipe commented on Nov 12, 2021

ptrtorain commented on Nov 13, 2021

Ansub commented on Dec 1, 2021

aeskafi commented on Dec 1, 2021

kedbirhan commented on Dec 4, 2021

Ansub commented on Dec 4, 2021

nlintas commented on Dec 5, 2021

Bazmundi commented on Dec 5, 2021

YousefAlsbaihi commented on Dec 14, 2021

zzz6519003 commented on Dec 14, 2021

jhkcia commented on Dec 27, 2021

ananshe commented on Jan 26, 2022

timothymureithi commented on Sep 24, 2022

xtRAVEN commented on Dec 2, 2022

HeyKalangi commented on Jul 15, 2023

Achal9099 commented on Jul 29, 2024

zzz6519003 commented on Jul 29, 2024

Achal9099 commented on Jul 29, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions