Create-react-app: Build fails: Could not find plugin "proposal-numeric-separator"

[amuehl]

[rosbel]

This started affecting my team as well

[Volosh1n]

Same here

[adascal]

Possible related to new babel-loader release (about 2 hours ago)
ref: https://github.com/babel/babel-loader/releases

[floofydoug]

affecting me as well.

[PFadel]

me too

[Simon-Bin]

me too

[gonzofish]

Hey everyone, thumbs up the original post. Adding "me too" just becomes noise to the maintainers

[existentialism]

This bug was fixed in Babel by https://github.com/babel/babel/pull/11201, and here once https://github.com/facebook/create-react-app/pull/8620 gets released.

[gonzofish]

Thanks @existentialism! Is there any solution/workaround in the meantime?

[vamci07]

I’m using [email protected], but still have the issue

[MKrupauskas]

Ejecting and updating the babel dependency would be a way of fixing this in the meantime.

[MMachado-uy]

+1

[apipemc]

affecting me as well.

[m-malik15]

I am getting the same error when building angular 8 app in azure deveops pipeline

"An unhandled exception occurred: [BABEL] D:\a\1\s\dist\web\main-es2015.02f4b8f684805898bcff.js: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "D:\a\1\s\node_modules\@babel\preset-env\lib\index.js")

[caballerojavier13]

+1

[daviguelfi]

Same problem here

[anthonyikeda]

For quick fix you can eject and downgrade babel-preset-react-app to 9.0.0(maybe more recent will work too)

Do you have a link on how I can achieve this? New to React/Node.

[Lukavyi]

For quick fix you can eject and downgrade babel-preset-react-app to 9.0.0(maybe more recent will work too)

Do you have a link on how I can achieve this? New to React/Node.

1. npm run eject
2. Open package.json and set "babel-preset-react-app": "9.0.0"
   (note: use exactly "9.0.0", not "^9.0.0")
3. npm i

[kuhel]

The issue is still reproduced

[rachelruderman]

Quick fix: Downgrading to "react-scripts": "^2.1.5", worked for my team!! No ejection necessary

EDIT: update thanks to @mohsenari:

I strongly suggest not using this as it results in 88 vulnerabilities from npm audit.
added 1940 packages from 744 contributors and audited 40593 packages in 44.492s found 88 vulnerabilities (81 low, 2 moderate, 5 high)

[nicolo-ribaudo]

:warning: Workaround :warning:

If you are using yarn, you can add this to your package.json:

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

If you are using npm, you can do the same thing but also need npm-force-resolutions

Then, don't forget to run yarn install or npm install.

EDIT: See https://github.com/facebook/create-react-app/issues/8680#issuecomment-601896916 for more detailed instructions for npm.

[anthonyikeda]

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

This worked for me as did the downgrading of react-scripts separately.

[salih7]

The problem is in babel-preset-react-app. For some reason when you install it, it strictly requires @babel/[email protected].

It looks like it's already updated to require @babel/[email protected] 11 days ago in the package.json for babel-preset-react-app.

I had to use the workaround above combined with using the npm-force-resolutions* package.

"scripts": {
  "preinstall": "npx npm-force-resolutions",
  ...
},
"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

_*Note that this requires a complete package-lock.json with the transitive dependencies that need updating._

This should only need to be done temporarily until the issue outlined above is fixed.

_Edit - Just want to add that I'm able to use [email protected]_

[leetmachine]

⚠️

Workaround if you are using yarn.

Add this to your package.json:

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

Worked for me, I also deleted node_modules and reinstall.

[Memogcia]

WARNING running command eject is one-way operation.

thanks to @nicolo-ribaudo, the solution works with react-scripts 3.3.1

As @leetmachine says delete node_modules and yarn.lock

[vamci07]

The problem is in babel-preset-react-app. For some reason when you install it, it strictly requires @babel/[email protected].

It looks like it's already updated to require @babel/[email protected] 11 days ago in the package.json for babel-preset-react-app.

I had to use the workaround above combined with using npm-force-resolutions package.

"scripts": {

preinstall: "npx npm-force-resolutions",

...

},

"resolutions": {

"@babel/preset-env": "^7.8.7"

}

This should only need to be done temporarily until the issue outlined above is fixed.

*Edit - Just want to add that I'm able to still use [email protected]

This worked for me...thanks

[aleciavogel]

This is what we get for deploying on a Friday... haha

Thanks everyone for the quick responses and easy workarounds! The package.json fix from @nicolo-ribaudo worked for us as well.

[MufidJamaluddin]

The problem is in babel-preset-react-app. For some reason when you install it, it strictly requires @babel/[email protected].
It looks like it's already updated to require @babel/[email protected] 11 days ago in the package.json for babel-preset-react-app.
I had to use the workaround above combined with using npm-force-resolutions package.
"scripts": {
preinstall: "npx npm-force-resolutions",
...
},
"resolutions": {
"@babel/preset-env": "^7.8.7"
}
This should only need to be done temporarily until the issue outlined above is fixed.
*Edit - Just want to add that I'm able to still use [email protected]

This worked for me...thanks

plus downgrade "babel-preset-react-app": "9.0.0"

[vicharzbecher]

⚠️ Workaround ⚠️

If you are using yarn, you can add this to your package.json:

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

If you are using npm, you can do the same thing but also need npm-force-resolutions

Then, don't forget to run yarn install or npm install.

Also worked for me, thanks

[ffrezende]

Thank you @nicolo-ribaudo.

[geneswitch]

I get this with preset-env workaround:

(venv-3.7.5) ➜  react git:(gene/fix-travis-20200320) ✗ npm install

> [email protected] preinstall /Users/thinkjones/switchboard/distillerizer/react
> npx npm-force-resolutions

npx: installed 5 in 2.693s
ENOENT: no such file or directory, open './package-lock.json'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] preinstall: `npx npm-force-resolutions`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/thinkjones/.npm/_logs/2020-03-20T19_41_51_842Z-debug.log

[nadeemc]

I get this with preset-env workaround:

(venv-3.7.5) ➜  react git:(gene/fix-travis-20200320) ✗ npm install

> [email protected] preinstall /Users/thinkjones/switchboard/distillerizer/react
> npx npm-force-resolutions

npx: installed 5 in 2.693s
ENOENT: no such file or directory, open './package-lock.json'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] preinstall: `npx npm-force-resolutions`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/thinkjones/.npm/_logs/2020-03-20T19_41_51_842Z-debug.log

I used these steps successfully--based on the excellent workarounds listed above, just consolidated multiple steps:

1. Install npm-force-resolutions
   npm i npm-force-resolutions --save-dev

2. Modify package.json

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

1. Run force-resolutions
   npx npm-force-resolutions

[salih7]

I get this with preset-env workaround:

(venv-3.7.5) ➜  react git:(gene/fix-travis-20200320) ✗ npm install

> [email protected] preinstall /Users/thinkjones/switchboard/distillerizer/react
> npx npm-force-resolutions

npx: installed 5 in 2.693s
ENOENT: no such file or directory, open './package-lock.json'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] preinstall: `npx npm-force-resolutions`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/thinkjones/.npm/_logs/2020-03-20T19_41_51_842Z-debug.log

The npm-force-resolutions package requires a package-lock.json with all your installed dependencies. I know it's annoying if you want to delete it and create it freshly, but the preinstall script will immediately fail if it doesn't exist (and it defeats the purpose of what it does). It will work fine in builds as long as you supply the package-lock.json

From their readme:

This packages modifies package-lock.json to force the installation of specific version of a transitive dependency (dependency of dependency), similar to yarn's selective dependency resolutions, but without having to migrate to yarn.

[mohsenari]

Quick fix: Downgrading to "react-scripts": "^2.1.5", worked for my team!! No ejection necessary

I strongly suggest not using this as it results in 88 vulnerabilities from npm audit.
added 1940 packages from 744 contributors and audited 40593 packages in 44.492s found 88 vulnerabilities (81 low, 2 moderate, 5 high)

[Demerjianm]

⚠️ Workaround ⚠️

If you are using yarn, you can add this to your package.json:

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

If you are using npm, you can do the same thing but also need npm-force-resolutions

Then, don't forget to run yarn install or npm install.

Thanks, worked for me 👍

[mohsenari]

For people who are looking for npm version of @nicolo-ribaudo 's workaround, here are the exact steps I took:

1. delete node_modules and package-lock.json
2. add "resolutions": { "@babel/preset-env": "^7.8.7" } to package.json
3. npm install npm-force-resolutions --save-dev
4. npm install
5. npx npm-force-resolutions
6. npm install again
7. npm run build

[cph2117]

For people who are looking for npm version of @nicolo-ribaudo 's workaround, here are the exact steps I took:

1. delete node_modules and package-lock.json
2. add "resolutions": { "@babel/preset-env": "^7.8.7" } to package.json
3. npm install npm-force-resolutions --save-dev
4. npm install
5. npx npm-force-resolutions
6. npm install again
7. npm run build

@mohsenari Is there a specific version of react-scripts required for this workaround?

[cristianounix]

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

[zameer-ansari]

For people who are looking for npm version of @nicolo-ribaudo 's workaround, here are the exact steps I took:

1. delete node_modules and package-lock.json
2. add "resolutions": { "@babel/preset-env": "^7.8.7" } to package.json
3. npm install npm-force-resolutions --save-dev
4. npm install
5. npx npm-force-resolutions
6. npm install again
7. npm run build

I had to add SKIP_PREFLIGHT_CHECK=true to .env file to make the build work without ejecting

[mohsenari]

@mohsenari Is there a specific version of react-scripts required for this workaround?

@cph2117 I don't believe so, I tested in two instances one with "react-scripts": "3.3.0" and another with "react-scripts": "3.4.0" in package.json

[Nirmal-Patel-Aleri]

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

I'm getting same error

[cristianounix]

@mohsenari what version of your babel-preset-env ?

[nicolo-ribaudo]

Anything higher than 7.8.6, or lower than 7.8.0, should work.

[Nirmal-Patel-Aleri]

@mohsenari what version of your babel-preset-env ?

its 7.8.4

[stenwie0591]

I found the same error during a deploy on Heroku. Has this happened to anyone else?
ps. i tried also for the Workaround, but it didn't worked!

[arinhouck]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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?

[whaberek]

@stenwie0591 solution with yarn work for me

"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

[pkibbey]

@mohsenari

I had a similar issue.

1. Enable package-lock in .npmrc.
2. Update all my npm dependencies to the latest versions
3. Follow resolutions/npm-force-resolutions step

Now I can build again.

[markwain]

Confirming the issue

[stenwie0591]

@arinhouck for me the error is:

Error: [BABEL] /tmp/build_9bf569961355c452d38b6129ae4a762b/client/src/index.jsx: Could not find plugin "proposal-numeric-separator". Ensure there is an entry in ./available-plugins.js for it. (While processing: "/tmp/build_9bf569961355c452d38b6129ae4a762b/client/node_modules/babel-preset-react-app/index.js$0")

I did a lot of rollback for a definitely working versions but still get the same error. I hope fix soon.

[ChrisEddy]

Rolling back react-scripts to 3.0.0 worked for me. Decided to go this route because it did not require ejecting or changing our build script to include the force resolve thing.

[enmanuelduran]

We bumped "@babel/preset-env": "^7.8.7" in our package.json and it fixed it for our team, we are using Yarn.

[vilhelmprytz]

Still broken?

[nicolo-ribaudo]

:warning:

Please add :+1: to existing comments if a solution worked for you, or if you have the same problem. New comments which don't add new information don't help.

[mruanova]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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",

[nicolo-ribaudo]

It should either be lower than 7.8.0 ("<7.8.0", or ~7.7.0), or higher than 7.8.6 (^7.8.7).

[simdad19]

non of the solutions working for me

[existentialism]

@arinhouck just fyi, but your issue is a bit different, check out https://github.com/babel/babel/pull/11298

[premp-cloud]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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\reactnode_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

[arinhouck]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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",

I did this and now I got the error about proposal-numeric-seperator locally

[nicolo-ribaudo]

@arinhouck 7.8.0-7.8.6 are the broken version. Try 7.8.7, 7.7.0 or 7.9.0.

[nicolo-ribaudo]

+1. Breaking the build on friday afternoon... for shame!

Please note that we fixed this bug 2 weeks ago in @babel/preset-env 7.8.7 :wink:

FYI, the bug was that @babel/preset-env 7.8.0-7.8.6 throw if we add any new feature to newer preset-env versions.

[arinhouck]

7.8.7

I switched to those versions (7.8.7 and 7.9.0) then received my previous error again

(plugin babel) ReferenceError: /Users/arinhouck/Documents/github/homelight-react/packages/core-ui/src/index.js: Unknown helper createSuper

[existentialism]

@arinhouck see my message above re: Unknown helper createSuper :)

[nicolo-ribaudo]

@arinhouck We have an open PR for that, I hope to release it soon.

[sebastianvz]

affecting me too ..

I try doing :

1. Update react.
2. npm run eject . this change whole package.json
3. npm-force-resolutions.

nothing works

[Wremeker]

same problem :)

[DatChoob]

Looks like Yarn users are having an easier time fixing this issue? Might have to switch.
Still having problems with npm

[carlos-soto]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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\reactnode_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\reactnode_modulesbabel-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.

[tacnoman]

The same here, I'm using npm instead of yarn and the solution with resolution in package.json doesnt work

[sebastianvz]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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\reactnode_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\reactnode_modulesbabel-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 ?

[nicolo-ribaudo]

@tacnoman Try adding "@babel/compat-data": "7.8.0" to your dev dependencies, it might work (it's not guaranteed to, it depends on npm hoisting)

[carlos-soto]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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\reactnode_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\reactnode_modulesbabel-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",

[TiKo98]

The problem is in babel-preset-react-app. For some reason when you install it, it strictly requires @babel/[email protected].

It looks like it's already updated to require @babel/[email protected] 11 days ago in the package.json for babel-preset-react-app.

I had to use the workaround above combined with using the npm-force-resolutions* package.

"scripts": {
  "preinstall": "npx npm-force-resolutions",
  ...
},
"resolutions": {
  "@babel/preset-env": "^7.8.7"
}

_*Note that this requires a complete package-lock.json with the transitive dependencies that need updating._

This should only need to be done until the issue outlined above is fixed.

_Edit - Just want to add that I'm able to use [email protected]_

All the suggested solutions did not work until I used preinstall hook! Now it works on localhost and on heroku in production mode.

[sebastianvz]

@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:

[!] (plugin babel) ReferenceError: /tmp/build_4c6997ef6fd5b4162d9721111196c3c8/packages/core-ui/src/index.js: Unknown helper createSuper

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\reactnode_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\reactnode_modulesbabel-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",

Doesn`t work for me

[ianschmitz]

Locking the thread to cut down on the excessive spam. We're actively working to make sure this is resolved. Please be patient.

[ianschmitz]

Waiting on https://github.com/babel/babel/pull/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]

Looks like we've fixed in #8661. Will be releasing shortly. Thanks for the patience everyone!

[ianschmitz]

This should be fixed in the 3.4.1 release.

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.

As always we recommend using and committing the package lock file to your repository.