-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
webpack-cli@3.3.1 postinstall: node ./bin/opencollective.js
npm ERR! Exit status 134
#878
Comments
@okonet Hi I try to install webpack-cli but i have this error 👎 npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: What can i do to solve this problem? |
Hi, thanks for reporting this. In order to understand what's the problem please fill the template provided when you created the issue. Also, please provide a repository to reproduce the error. Thanks :) |
Could you give a complete stack trace after removing node modules and running npm install again? |
webpack-cli v.3.2.2 comes with a fix for this. |
Repo orgs: Can someone remove me from the project. I’m reviving too many emails and I’m not even working on it. Thanks! Everyone else: please don’t mention people in issues if this isn’t really necessary. |
Will do this tomorrow Andrey. Hope you’re doing well! 🤗 |
@evenstensberg I'm getting the same error when trying to install webpack-cli globally... there's no specific errors to check.. I tried different approach but with no luck... please help. :( |
Hi @dev-xror, thanks for reporting this, could you please open a new Issue? Also:
|
Does it fixed? I am using webpack-cli 3.3.2 now, but I still get the same error
'node' ▒▒▒▒▒ڲ▒▒▒▒ⲿ▒▒▒Ҳ▒▒▒ǿ▒▒▒▒еij▒▒▒ npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
The most updated conversation about this is #870:
|
Hi, |
Hi! v3.3.3 has just been released with a fix for this. I suggest you to try it and if you still have this problem you can open a new detailed issue :) |
Describe the bug
A 💯 way to do this is to provide your configuration via a GitHub gist and/or to use markdown when describing which commands you used when the error occurred! Be precise and clear in your description of the bug.
What is the current behavior?
This is where you elaborate on the current behavior of the cli, how it behaves normally differing from the previous version/build you did.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Please paste the results of
webpack-cli info
here, and mention other relevant informationAdditional context
Add any other context about the problem here like linking to an similar issue you might think is the cause.
The text was updated successfully, but these errors were encountered: