-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Auto-Install fails on some OS/node combinations #1168
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
Labels
Comments
So it seems The solution was actually pretty simple - something got lost in a merge/rebase. #1170 by @sudo-suhas should fix this. could any of you run this and test it out?
|
@LinusBorg fix works for me, thanks! |
@LinusBorg Solved the problem by using cmd "vue init webpack#develop", Thank you! |
The fix is now available though the normal command as well. |
Thanks for testing and reporting back! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem:
For the original bug report, see vuejs/vue-cli#681
Immediate solutions/workarounds.
One thing we can immediately improve is the error handling. This error is not "fatal" - all people have to do is run
npm install
themselves. So I will add a nice error message explaining that to users.so what's the Problem, really?
As to the original source of the problem, I'm a bit dumbfounded for the moment.
That would be weird - being in the wrong directory should lead to an error on OSX as well, but doesn't (for me).
I also think I set the cwd for the npm call to the right directory here:
https://github.com/vuejs-templates/webpack/blob/develop/meta.js#L155-L158
The text was updated successfully, but these errors were encountered: