Could not find plugin "proposal-numeric-separator"

Question

How to fix Could not find plugin "proposal-numeric-separator", I get this error when I try to build my React application, I have not ejected the application yet:

./src/index.js
Error: [BABEL] /home/pc/Downloads/project/src/index.js: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "/home/pc/Downloads/project/node_modules/babel-preset-react-app/index.js$0")
    at Array.map (<anonymous>)
    at Generator.next (<anonymous>)
    at Generator.next (<anonymous>)


error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I have tried to download Babel and the dependency Proposal Numeric Separator, remove the Node Modules, clean the Yarn cache; but nothing worked.

I'm using Yarn 1.22.4 and Node 13.11.0, but I have also tried with NPM 6.13.7.

Other people are having the same issue: https://www.reddit.com/r/angular/comments/flymj5/build_failing_please_help/ The suggested solution did not work for me. — peoplespete, Mar 20 '20 at 20:45

score 92 · Accepted Answer · edited Jul 19 '20 at 19:27

92

The following steps work:

Add the following line to package.json:

"resolutions": { 
  "@babel/preset-env": "7.5.5" 
},

Run the following command:

$ npx npm-force-resolutions

Install dependencies:

$ npm install
# or 
$ yarn

Build your project:

$ yarn build

Take a look at this Github Issue

edited Jul 19 '20 at 19:27

glinda93

7,659
5
40
78

answered Mar 20 '20 at 21:13

Hillkim Henry

2,841
13
17

2

Just added `resolutions`, removed *node_modules* and installed the dependencies. It worked, thanks. **Observation**: I have tested the build and everything is ok. – Mar 20 '20 at 21:48
2

man, you save my life. How do you know about this answer? You have got my awesome like, buddy. Thanks a lot. – Carlos Querioz Mar 21 '20 at 00:35
1

@CarlosQuerioz I think that the reason is the last topic from [this](https://classic.yarnpkg.com/en/docs/selective-version-resolutions/#toc-why-would-you-want-to-do-this) documentation: "Your dependency defines a broad version range and your sub-dependency just got a problematic update so you want to pin it to an earlier version" – Mar 21 '20 at 01:40
1

Thank you man. I don't know what happened. How does it happen suddenly. I coul build it normally until yesterday and today I had to do this to fix it? – user3746480 Apr 10 '20 at 11:37
2

@user3746480 It is a problem with the babel dependencies. The most probable cause might be removing or updating node modules. Thats why enforcing a given working version fixes it – Hillkim Henry Apr 10 '20 at 22:41
awsome, in my case, after running audit fix command ran into this issue thanks for a day, be careful guys while running such command while it may be essential but at the cost of a day – Naga Aug 07 '20 at 21:08

Wahab Shah · Answer 2 · 2020-04-16T19:43:54.093

62

Try this, it works: npm i @babel/compat-data@7.8.0

I have just used it like 10 minutes ago, and it's working fine.

Related issue going on github about this. Click Here!

edited Apr 16 '20 at 19:43

answered Mar 25 '20 at 12:14

Wahab Shah

2,066
1
14
19

1

Works for me. Most straight-on answer IMHO. – El Mac Mar 27 '20 at 18:55
Happy to hear that, Thanks Andy B-) – Wahab Shah Jun 12 '20 at 12:40
Thanks, I tired the other methods described here but this worked on the first try – Garth Humphreys Jun 14 '20 at 18:15
My installed @babel/preset-env version is 7.8.6 and installing the exact same version of @babel/compat-data worked for me! – efeder Aug 17 '20 at 13:42
1

Update: this is still working. Thanks! – Kobi Apr 08 '22 at 13:12
@Kobi I am glad it is. Have a great weekend :) – Wahab Shah Apr 09 '22 at 05:40

score 16 · Answer 3 · answered Mar 22 '20 at 19:46

16

From the corresponding issue in create-react-app,

Update react-scripts to 3.4.1 in your package.json file and remove node_modules as well as package-lock.json/yarn.lock and re-install.

answered Mar 22 '20 at 19:46

jobinbasani

2,075
6
47
66

Badis Merabet · Answer 4 · 2020-03-28T18:56:59.040

Why this problem happened?:

It's an issue of conflicts between internal packages used by babel.

Adding a new plugin to @babel/compat-data breaks old @babel/preset-env versions. This is because preset-env iterates over compat-data's plugins, and throws if the plugin isn't defined in preset-env's available-plugins.js file.

This is the merge that fixed the issue: https://github.com/babel/babel/pull/11201/files/a88a00750c61ff89f1622d408d67108719f21ecd

Solution:

Delete package-lock.json or yarn.lock
Delete node_modules folder
In package.jon I have adjusted the version numbers of these packages to:

    ...
    "devDependencies": {
        "@babel/compat-data": "^7.8.0",
        "@babel/preset-env": "^7.8.0",
        "babel-loader": "^8.1.0",
        ...
    },
    ...
    "resolutions": {
        "@babel/preset-env": "^7.8.0"
    }

Run npm install
Run npm run build

score 9 · Answer 5 · answered Mar 24 '20 at 12:28

Reference: https://github.com/angular/angular-cli/issues/17262

I found two solution

a ) Install babel compat

"devDependencies": {
    "@babel/compat-data": "7.8.0",
}

b) Install plugin-proposal-numeric-separator

npm install --save-dev @babel/plugin-proposal-numeric-separator

install this version only 7.8.0

Angular CLI can create this kind of issue. Go to package json and change it to

build-angular": "0.803.17"

please don't add ^ or ~ .

score 7 · Answer 6 · answered Mar 22 '20 at 15:08

I faced similar issue and i was able to fix it by updating all babel dependencies to latest version. I'm not aware of the exact issue with babel. However, the below mentioned step worked for me.

Step 1: identify and remove all babel related dependencies from package.json

npm remove @babel/runtime @babel/core @babel/plugin-proposal-class-properties @babel/plugin-transform-modules-commonjs @babel/plugin-transform-runtime @babel/preset-env @babel/preset-react babel-eslint babel-jest babel-loader

Step 2: re-install babel dependencies

npm install --save @babel/runtime

npm install --save-dev @babel/core @babel/plugin-proposal-class-properties @babel/plugin-transform-modules-commonjs @babel/plugin-transform-runtime @babel/preset-env @babel/preset-react babel-eslint babel-jest babel-loader

PS: The above list of babel dependencies will differ for your project.

score 7 · Answer 7 · answered Mar 23 '20 at 18:42

7

I just changed react-script version from 3.0.1 to 3.4.1

answered Mar 23 '20 at 18:42

Beatriz Cibele

71
4

score 7 · Answer 8 · edited Mar 28 '20 at 22:08

7

You can use this command, which has worked for me.

npm i @babel/compat-data@7.8.0

edited Mar 28 '20 at 22:08

Dharman

30,962
25
85
135

answered Mar 28 '20 at 20:21

M Danial

166
1
4

Furqan S. Mahmoud · Answer 9 · 2020-03-24T11:28:38.877

5

I'm using angular & this worked for me, simply changed the version of @babel/compat-data from ^7.8.0 to just 7.8.0, the package-lock.json is having newer version which has bugs.

Inside package.json:

  "devDependencies": {
    "@babel/compat-data": "7.8.0",
}

edited Mar 24 '20 at 11:28

answered Mar 24 '20 at 10:20

Furqan S. Mahmoud

1,417
2
13
26

1

yes "@babel/compat-data": "7.9.0", doesn't work https://github.com/angular/angular-cli/issues/17262#issuecomment-603396857 – Gerardo Perrucci Mar 27 '20 at 18:47

score 5 · Answer 10 · answered Mar 27 '20 at 18:44

In package.json

  "dependencies": {
    "@babel/compat-data": "7.8.0",
    "@babel/plugin-proposal-numeric-separator": "^7.8.3",
    "babel-loader": "^8.1.0",
  ....
  "resolutions": {
     "@babel/preset-env": "^7.8.7"
  }

it is working for me. You can read more

https://github.com/angular/angular-cli/issues/17262#issuecomment-603396857

score 4 · Answer 11 · answered Mar 24 '20 at 14:25

Its just a 4 step process.

Reason: This happens because of a package missing in babel. This will happen even if you create angular app using ng new command.

Solution

Install plugin-proposal-numeric-separator using the following code in terminal.
```
npm install --save @babel/plugin-proposal-numeric-separator
```
Once it is done navigate to the file as shown below.

node_modules > @babel > preset-env > available-plugins.js

In available-plugins.js below exports.default = void 0; copy and paste the following code.

var _pluginProposalNumericSeparator = _interopRequireDefault(require("@babel/plugin-proposal-numeric-separator"));

In available-plugins.js within var _default object declaration copy and paste the following code.
```
"proposal-numeric-separator": _pluginProposalNumericSeparator.default,
```

And it is done.

I think that is not a valid solution, please follow this thread: https://stackoverflow.com/questions/60780664/could-not-find-plugin-proposal-numeric-separator/60892324#60892324 — Gerardo Perrucci, Mar 27 '20 at 18:46

score 4 · Answer 12 · answered Mar 27 '20 at 16:26

In my angular 8 application, although I did not have any direct dependancy of react-scripts package and did not have it in package.json either but started getting this error on build. It was likely used as a depedancy by other packges.

By reading this post on github, I added it as dependancy in package.json "react-scripts": "3.4.1" and run npm install the build started working just fine.

score 4 · Answer 13 · answered Apr 23 '20 at 13:14

4

This worked for me:

Delete package-lock.json
Delete node_modules
Run npm i

answered Apr 23 '20 at 13:14

Eric Eskildsen

4,269
2
38
55

score 1 · Answer 14 · answered Jul 19 '20 at 05:41

1

try this , this working with me .

npm i @babel/compat-data@7.8.0

answered Jul 19 '20 at 05:41

Abd Abughazaleh

4,615
3
44
53

Zameer Ansari · Answer 15 · 2020-04-18T13:39:20.580

0

Add SKIP_PREFLIGHT_CHECK=true to .env file to make the build work without ejecting and follow the below steps:

Delete node_modules and package-lock.json
Add "resolutions": { "@babel/preset-env": "^7.8.7" } to package.json
Run npm install npm-force-resolutions --save-dev
Run npm install
Run npx npm-force-resolutions
Run npm install again
Run npm run build

edited Apr 18 '20 at 13:39

answered Apr 18 '20 at 13:25

Zameer Ansari

28,977
24
140
219

score 0 · Answer 16 · answered Jun 03 '20 at 20:28

0

In my case I've got a corrupted node_modules folder. My yarn install simply stopped in the middle by a power surge.

By running:

rm -rf node_modules
yarn

My problem was solved.

answered Jun 03 '20 at 20:28

Christian Saiki

1,568
15
22

score 0 · Answer 17 · answered Jun 19 '20 at 05:38

0

worked for me. npm install @babel/compat-data@~7.8.0

answered Jun 19 '20 at 05:38

Ankur Garg

151
2
2

score -2 · Answer 18 · answered Mar 20 '20 at 20:42

-2

I just had this happen to me. The To fix it I ran yarn build with sudo privileges.

answered Mar 20 '20 at 20:42

Noah Cote

23
1
2

Could not find plugin "proposal-numeric-separator"

18 Answers18

Linked

Related