-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: node -e "try{require('./postinstall')}catch(e){}" #729
Comments
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. |
When installing multiple packages that depend on core-js, the postinstall message will pop up mutiple times which will add unnecessary verbosity to the terminal log. I know zloirock#767, zloirock#548, zloirock#797, zloirock#757, zloirock#781 ,zloirock#729, zloirock#708, refer to this problem and since @zloirock refuses to remove this, lets limit it to one time so that verbosity gets truncated to the least.
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 |
Even I'm getting above message/warning:
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:
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
|
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:
The text was updated successfully, but these errors were encountered: