-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
cmd automatically closed after running vue init
#274
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
Comments
It might not be related at all, but I had many problems with yarn@0.18.1 yesterday. After I re-installed everything with npm things started to work again. Please try it out, it might help, otherwise let us know. |
@zigomir Yep, I tried npm yesterday and it did work. I'm just very curious to know if it is fine to use yarn to install vue-cli. |
@c-cho yes, it's absolutely fine 🙂 |
@posva But as shown above, vue-cli installed with yarn (not npm) didn't work for me.. |
Seems to be an issue with yarn: yarnpkg/yarn#1601 |
@posva Okay, I will keep an eye on it. |
Just saw this, I can confirm this is fixed with v0.19.1 (possibly v0.19 too). |
Uh oh!
There was an error while loading. Please reload this page.
I installed vue-cli by using yarn(
yarn global add vue-cli
) today.It seems that everything went successfully.
But when I tried to initialize a vue project with command like
vue init webpack test
,cmd closed itself automatically.
After some research, I found that it occurred because vue.cmd which located in
C:\Users\<MyUserName>\AppData\Local\Yarn\config\global\node_modules\.bin
couldn't be found in this script"$basedir/../../Users/<MyUserName>/AppData/Local/Yarn/config/global/node_modules/.bin/vue.cmd"
Looking to #245 , I think yarn support is already taken into account, but I'm wondering whether it is OK to install vue-cli with yarn in Windows.
OS: Windows 7
yarn: 0.18.1
nodejs: 6.2.0 (x64)
npm: 3.8.9
Thanks in advance.
The text was updated successfully, but these errors were encountered: