Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in the package.json of a module in node_modules

Question

This is a React web app. When I run

npm start

This error occurred

> dataflow@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/juliantc/Desktop/ai-studio/development/frontend/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.<anonymous> (/Users/juliantc/Desktop/ai-    studio/development/frontend/node_modules/postcss-safe-parser/lib/safe-parser.js:1:17) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v17.0.1

This error only occurs when I run this on this specific computer, which I do not have superuser access to. It works on other computers.

For reference, this is ./node_modules/postcss-safe-parser/node_modules/postcss/package.json

{
  "name": "postcss",
  "version": "8.2.6",
  "description": "Tool for transforming styles with JS plugins",
  "engines": {
    "node": "^10 || ^12 || >=14"
  },
  "exports": {
    ".": {
      "require": "./lib/postcss.js",
      "import": "./lib/postcss.mjs",
      "types": "./lib/postcss.d.ts"
    },
    "./": "./"
  },
  "main": "./lib/postcss.js",
  "types": "./lib/postcss.d.ts",
  "keywords": [
    "css",
    "postcss",
    "rework",
    "preprocessor",
    "parser",
    "source map",
    "transform",
    "manipulation",
    "transpiler"
  ],
  "funding": {
    "type": "opencollective",
    "url": "https://opencollective.com/postcss/"
  },
  "author": "Andrey Sitnik <andrey@sitnik.ru>",
  "license": "MIT",
  "homepage": "https://postcss.org/",
  "repository": "postcss/postcss",
  "dependencies": {
    "colorette": "^1.2.1",
    "nanoid": "^3.1.20",
    "source-map": "^0.6.1"
  },
  "browser": {
    "./lib/terminal-highlight": false,
    "colorette": false,
    "fs": false
  }
}

And this is what I get when I list the files in ./node_modules/postcss-safe-parser/node_modules/postcss/lib/

lgtd-lt-119-mbmt:frontend juliantc$ ls ./node_modules/postcss-safe-parser/node_modules/postcss/lib/

at-rule.d.ts        css-syntax-error.d.ts   input.d.ts      map-generator.js    postcss.d.ts        processor.js        rule.js         tokenize.js
at-rule.js      css-syntax-error.js input.js        node.d.ts       postcss.js      result.d.ts     stringifier.js      warn-once.js
comment.d.ts        declaration.d.ts    lazy-result.d.ts    node.js         postcss.mjs     result.js       stringify.d.ts      warning.d.ts
comment.js      declaration.js      lazy-result.js      parse.d.ts      previous-map.d.ts   root.d.ts       stringify.js        warning.js
container.d.ts      fromJSON.d.ts       list.d.ts       parse.js        previous-map.js     root.js         symbols.js
container.js        fromJSON.js     list.js         parser.js       processor.d.ts      rule.d.ts       terminal-highlight.js

Try reinstalling node packages. – vishwas meshram Oct 24 '21 at 07:20 — vishwas meshram, Oct 24 '21 at 07:20
I did but the same thing happened again and again – Julian Chu Oct 24 '21 at 08:01 — Julian Chu, Oct 24 '21 at 08:01

score 114 · Accepted Answer · edited Nov 13 '21 at 18:36

114

I am also stuck with the same problem because I installed the latest version of Node.js (v17.0.1).

Just go for node.js v14.18.1 and remove the latest version just use the stable version v14.18.1

nvm uninstall <version>

OR

nvm uninstall v17.0.1

then install the LTS one which is v14.18.1

nvm install --lts

This worked for me.

edited Nov 13 '21 at 18:36

Dada

5,692
6
21
39

answered Oct 24 '21 at 16:34

Anmol Noor

1,298
1
6
6

2

you dont need to uninstall the node version btw if you dont want to. you can use an nvmrc file in the project folder, or set a different version as the nvm default – eltonkamami Nov 07 '21 at 18:01
so this problem is of installing new version of npm?!! i had this problem too :( – fatemeh kazemi Nov 21 '21 at 10:23
1

@fatemehkazemi yes it is due to maybe some bug or maybe some old version of settings that exist in our project ... – Anmol Noor Nov 21 '21 at 12:18
today i had the exact same problem, installing the lts version solved the issue. before i've done an install of the current node version and upgraded the npm. but this is only my observation not a root cause analysis. – Thomas Poth Dec 05 '21 at 11:07
2

Thanks! This worked. Couldn't have thought this would be the problem. Cheers – Abhik Banerjee Feb 18 '22 at 12:47

score 45 · Answer 2 · answered Oct 25 '21 at 10:03

45

Remove node_modules folder and .lock file and re-install your packages (yarn or npm). It worked for me with last 17.0.1 of nodejs, I can npm (or yarn) start my app again.

answered Oct 25 '21 at 10:03

laugre

459
2
2

2

That worked for me but then I got a `Error: error:0308010C:digital envelope routines::unsupported at new Hash (node:internal/crypto/hash:67:19)` and that was that :/. – Chris Oct 26 '21 at 22:17
2

workaround there -> https://stackoverflow.com/questions/69692842/error0308010cdigital-envelope-routinesunsupported – laugre Oct 28 '21 at 13:08
worked for me too – Gunesh Shanbhag Dec 10 '21 at 20:36
1

@GuneshShanbhag IMHO, to second a comment, it's better to hit the +1 button than post a new comment. – Pablion Dec 14 '21 at 22:41
Ugh. Not for me - `graphql-request` doesn't like it (specifically the message reads `error graphql-request@3.2.0: The engine "node" is incompatible with this module. Expected version "10.x || 12.x || 14.x". Got "17.0.1"`). – BogeyMan Dec 17 '21 at 02:23
1

@BogeyMan another issue that could lead to creating a new thread... Maybe you should upgrade your graphql-request version to the last one, check before which version is compatible with Nodejs 17.0.1. But be careful with your project other peer dependencies. – laugre Dec 20 '21 at 10:46

score 20 · Answer 3 · edited Nov 03 '21 at 05:00

20

Roll back to Node 16.8.0 or (works for me) stable version 16.13.0:

Step 1: install n

npm install -g n

Step 2: install/set node latest stable version

sudo n stable

or set 16.8.0

sudo n 16.8.0

Note, if you can't or don't want to use sudo for n, you can set environment variables for the location, eg;

export N_PREFIX=$HOME/.n
export PATH=$N_PREFIX/bin:$PATH

edited Nov 03 '21 at 05:00

Daniel Pickering

3
2

answered Oct 27 '21 at 18:37

Stijn Bakker

201
2

score 20 · Answer 4 · edited Nov 18 '21 at 14:46

20

my working solution was with yarn:

removed /node_modules and yarn.lock file.
then reinstalled my deleted packages/file using yarn install .

it worked !!!

edited Nov 18 '21 at 14:46

Abilogos

4,334
2
16
37

answered Nov 18 '21 at 12:30

keshgurung

201
1
4

1

Didn't work for me. – cheznead Feb 08 '22 at 20:51
1

Worked for me on node version 17.4.0 on a Macbook. I was building a Shopify custom App. – SanjoS30 Feb 22 '22 at 07:53
Worked for me as well. Thanks! – Quang Trần May 04 '22 at 08:07

score 20 · Answer 5 · answered Nov 24 '21 at 13:22

FWIW, I bumped into this issue on macOS Monterey with Node 17.0.1 installed via Homebrew. Downgrading to Node 16.x worked for me.

Downgrade from Node 17.x (latest) to Node 16.x using Homebrew:

brew uninstall --ignore-dependencies node
brew install node@16
brew link node@16

score 17 · Answer 6 · answered Nov 01 '21 at 00:06

17

removing and reinstalling lock and node modules didn't help but npm update worked for me

answered Nov 01 '21 at 00:06

apinanyogaratnam

516
3
12

Literally this is it... Despite the "more specific" answer re macOS Monterey from Rob van der Leek below; I'm on Monterey running node `v17.0.1` from Homebrew and this was the fix! Thanks! – lol Nov 27 '21 at 01:06
This worked for me too, I'm on Catalina running node v17.3.0. Thanks! – Alex Jan 22 '22 at 09:29

score 7 · Answer 7 · answered Dec 04 '21 at 22:58

7

I also get the error when using Node.js v17.0.1 (Lates Features) - I am using macOS Catalina and homebrew.

So I want to switch Node.js v17.0.1 to Node.js (LTS) -> Node.js v16.3.1

I uninstall node using homebrew with the following command:

brew uninstall node

Then I download Node LTS from https://nodejs.org/en/ and install it.

That is work for me. Thanks :)

answered Dec 04 '21 at 22:58

Rahmat Oktrifianto

301
2
7

Always install with brew. – Michal Dec 08 '21 at 23:20
This should be the answer – puerile Dec 19 '21 at 19:14
It is definitely a version issue. I used `n` to switch versions to stable – TrySpace Dec 20 '21 at 21:08

score 4 · Answer 8 · answered Nov 13 '21 at 21:16

4

After removing node_modules & package-lock.json, I ran

npm audit fix --force

& updated react-scripts to the latest available version with

npm install react-scripts@latest

answered Nov 13 '21 at 21:16

Oli

121
3
4

score 4 · Answer 9 · edited Jan 31 '22 at 17:22

4

I just did:

npm update
npm start

worked for me.

edited Jan 31 '22 at 17:22

Skatox

4,147
11
42
46

answered Nov 14 '21 at 22:02

Raz

69
1

2

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Nov 15 '21 at 02:33

score 2 · Answer 10 · answered Dec 07 '21 at 09:23

2

Remove node_module & package-lock.json

then

npm install

( in install if you get error as to use --force and --legacy-peer-deps the command as

`npm install --legacy-peer-deps`

)

npm start

answered Dec 07 '21 at 09:23

Mahesh More

114
6

score 2 · Answer 11 · answered Dec 29 '21 at 17:19

2

An update to the latest version of "react-scripts" have been worked for me! Previous "react-scripts" version was 4.0.3 and I've updated to 5.0.0. Node version is 17.0.1.

answered Dec 29 '21 at 17:19

Den Skulimovskiy

31
3

score 1 · Answer 12 · answered Nov 17 '21 at 11:31

1

If you use yarn you can:

rm -rf node_modules yarn.lock
yarn add -D react-scripts@latest
yarn build

For npm:

rm -rf node_modules package-lock.json
npm install -D react-scripts@latest
npm install
npm run build

answered Nov 17 '21 at 11:31

Oded BD

2,148
21
26

score 1 · Answer 13 · answered Nov 17 '21 at 18:38

1

I faced similar issue and it was due to node version v17.1.0.

I have nvm with 3 different versions of node installed. Just switched to version v14.18.1 using nvm and the issue resolved.

answered Nov 17 '21 at 18:38

Arif Shaikh

81
2
10

score 1 · Answer 14 · answered Jan 24 '22 at 20:20

I was receiving Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/parser' is not defined by "exports" in ...node_modules\next\node_modules\postcss\package.json

I have resolved it on node version 17.4.0 after I upgraded react, and nextjs using:

npm install react@latest react-dom@latest
npm install next@12

(https://nextjs.org/docs/upgrading)

score 0 · Answer 15 · answered Jan 31 '22 at 08:07

Uninstalling the current Node.js and installing LTS solves the problem, but if you want to keep the currently installed version, you could use nvs add lts to install the latest Node.js LTS, and activate it using nvs use node/<lts version>/<platform>. The LTS version and Platform values will be provided in the first command output.

score 0 · Answer 16 · answered Apr 12 '22 at 13:03

I don't get why @AnmolNoor wants you to uninstall version 17.

The proper way:

Make sure you have nvm (https://github.com/nvm-sh/nvm). If you don't, I highly recommend installing it.
Check your node --version
If the version is 17, this might be the reason for the error (as it was in my case)
Run nvm install 14. After installing is complete, it should also switch your node version to 14.
Check the version node --version just in case. If you still see 17, run nvm use 14

Your node --version should now be 14.

Note: Every time you close the current terminal tab, your default node version will return back to 17 unless you change this.

Next time you have to switch node version to 14, you don't have to install it again, just run nvm use 14

Macedo_Montalvão · Answer 17 · 2022-04-24T11:55:21.770

I had the same problem 5 minutes ago, which is strange because it was working, but anyway, in my case the problem was in version 3.0 of the package "resolve-url-loader", after upgrading to version 5.0, everything has been resolved.

npm i resolve-url-loader@^5.0.0 --save-dev

If you have this package and node 17+, try to update it to the latest version, outdated versions cause problems like this.

If you hit an error in your application with Node.js 17, it’s likely that your application or a module you’re using is attempting to use an algorithm or key size which is no longer allowed by default with OpenSSL 3.0. A command-line option, , has been added to revert to the legacy provider as a temporary workaround for these tightened restrictions.ERR_OSSL_EVP_UNSUPPORTED--openssl-legacy-provider

For details about all the features in OpenSSL 3.0 please see the OpenSSL 3.0 release blog.

Contributed in https://github.com/nodejs/node/pull/38512, https://github.com/nodejs/node/pull/40478

https://nodejs.org/en/blog/release/v17.0.0/#openssl-3-0

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/tokenize' is not defined by "exports" in the package.json of a module in node_modules

17 Answers17

Linked