Please fix this error. Three days ago, my project does not have any error. But now, it has some bug, the Popover in react-boostrap does not show where I want.
When I install packages, the terminal show:

I don't see any errors. What do you mean?
I don't know why it is. But I thinks it makes my source code be incorrect. If this is not the reason, I will close this issue. Thanks for your support.
Seems it's not the reason.
@dantn93 I have the same issue on Windows 7. The issue seems to be with core-js postinstall script.
At the moment, it is not possible to install react-scripts package. Or any package that relies on core-js postinstall script.
If it can be of any help, after a few hours of research, I solved this error by just cancelling Node debugger which I activated in NODE_OPTIONS env var, set with --inspect.
After an export NODE_OPTIONS="", I didn't have this issue anymore.
Even I'm getting above message/warning:
[email protected] postinstall E:\Hitachi_Vantara\Code\Front_End\Eris\node_modules\babel-runtime\node_modules\core-js
node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
https://opencollective.com/core-js
https://www.patreon.com/zloirock
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
[email protected] postinstall E:\Hitachi_Vantara\Code\Front_End\Eris\node_modules\core-js
node -e "try{require('./postinstall')}catch(e){}"
[email protected] postinstall E:\Hitachi_Vantara\Code\Front_End\Eris\node_modules\core-js-pure
node -e "try{require('./postinstall')}catch(e){}"
same error with my code i don't understand how to resolve this create-react-app doen't work because of this

same error with my code i don't understand how to resolve this create-react-app doen't work because of this
same error found any fix!!!
Most helpful comment
If it can be of any help, after a few hours of research, I solved this error by just cancelling Node debugger which I activated in
NODE_OPTIONSenv var, set with--inspect.After an
export NODE_OPTIONS="", I didn't have this issue anymore.