You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Build fails: Could not find plugin "proposal-numeric-separator" #8680
Running npm run build will fail on any project, even on a vanilla app created with create-react-app will fail with the following error:
Error: [BABEL] /Users/<username>/Projects/my-app/src/index.js: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "/Users/<username>/Projects/my-app/node_modules/babel-preset-react-app/index.js$0")
at Array.map (<anonymous>)
at Generator.next (<anonymous>)
at Generator.next (<anonymous>)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app@0.1.0 build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
From our build pipelines I can tell it started roughly around Mar 20, 2020 4:48pm GMT+0100
Did you try recovering your dependencies?
I tried recovering the module tree and even verified with a vanilla app. It happens on my local machine and on our build machines with no changes involved there.
Hey everyone, thumbs up the original post. Adding "me too" just becomes noise to the maintainers
Reacted by Vsevolod Voloshyn, Pedro Fadel, Eduardo Borges, Doug, Arnold Asllani, Evan Emolo, Rachel, Taras Lukavyi, Amephist, Jonathan J. Watson and 28 more
Reacted by Matt Fehskens, Vsevolod Voloshyn, muehlbaueralex, Mykolas Krupauskas, Pedro Fadel, Taras Lukavyi, Nicolò Ribaudo, Javier Caballero, Gene, Evandro Terra and 4 more
Reacted by muehlbaueralex, Mykolas Krupauskas, Pedro Fadel, Arnold Asllani, Taras Lukavyi, Chris Russell-Walker, Javier Caballero, Nicolas Figueredo, Evandro Terra, Kabeer and 3 more
@stenwie0591 our team is also experiencing error on Heroku deploy for a node react app using yarn. Workaround is not doing anything for us either.
We are seeing the following error:
Not seeing the issue happen when building locally, however specified "@babel/preset-env": "^7.8.0", and ran yarn install and then it reproduced locally. It seems like heroku is bumping or not respecting lock file?
if it is bumping or not respecting then remove the caret likes this: "@babel/preset-env": "7.8.0",
Heroku updates the dependencies - hence the error.
We got this locally itself. npm update was good but the error appeared in npm start.
Starting the development server...
Failed to compile.
./node_modules/react-dev-utils/webpackHotDevClient.js
Error: [BABEL] C:\projects\react\node_modules\react-dev-utils\webpackHotDevClient.js: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "C:\projects\react\node_modules\babel-preset-react-app\dependencies.js$0")
at Array.map ()
at Generator.next ()
Tried with "react-scripts": "3.4.0", and "react-scripts": "3.4.0" - no success.
Changed @babel/preset-env": "^7.8.7" - no success
I had to downgrade "react-scripts" to "3.0.0" for now, thee npm-force-resolutions approach didn't work for me on npm.
How did you do the downgrade ?
Just change your package.json to:
"react-scripts": "3.0.0",
Activity
rosbel commentedon Mar 20, 2020
Volosh1n commentedon Mar 20, 2020
adascal commentedon Mar 20, 2020
Possible related to new
babel-loaderrelease (about 2 hours ago)ref: https://github.com/babel/babel-loader/releases
floofydoug commentedon Mar 20, 2020
PFadel commentedon Mar 20, 2020
Binbiubiubiu commentedon Mar 20, 2020
me too
gonzofish commentedon Mar 20, 2020
Hey everyone, thumbs up the original post. Adding "me too" just becomes noise to the maintainers
existentialism commentedon Mar 20, 2020
This bug was fixed in Babel by babel/babel#11201, and here once #8620 gets released.
gonzofish commentedon Mar 20, 2020
Thanks @existentialism! Is there any solution/workaround in the meantime?
marvelousdev0 commentedon Mar 20, 2020
I’m using babel-loader@8.0.6, but still have the issue
MKrupauskas commentedon Mar 20, 2020
Ejecting and updating the babel dependency would be a way of fixing this in the meantime.
MMachado-uy commentedon Mar 20, 2020
+1
apipemc commentedon Mar 20, 2020
62 remaining items
carlos-soto commentedon Mar 20, 2020
Just change your package.json to:
"react-scripts": "3.0.0",
TimKochDev commentedon Mar 20, 2020
All the suggested solutions did not work until I used preinstall hook! Now it works on localhost and on heroku in production mode.
sebastianvz commentedon Mar 20, 2020
ianschmitz commentedon Mar 20, 2020
Locking the thread to cut down on the excessive spam. We're actively working to make sure this is resolved. Please be patient.
ianschmitz commentedon Mar 20, 2020
Waiting on babel/babel#11298 to be merged and released then we should be able to bump the versions on our side and release (hopefully!).We think #8681 should resolve this without the PR from babel side as we shouldn't encounter that specific scenario here.
ianschmitz commentedon Mar 20, 2020
Looks like we've fixed in #8661. Will be releasing shortly. Thanks for the patience everyone!
ianschmitz commentedon Mar 21, 2020
This should be fixed in the 3.4.1 release.
Update
react-scriptsto3.4.1in yourpackage.jsonfile and removenode_modulesas well aspackage-lock.json/yarn.lockand re-install.As always we recommend using and committing the package lock file to your repository.