ERROR when use vue create

[vvpvvp]

Version

3.0.0-alpha.13

Reproduction link

http://www.heyui.top/

Steps to reproduce

npm create test1
Please pick a preset: default (babel, eslint)

What is expected?

create successfull

What is actually happening?

ERROR command failed: npm install --loglevel error --registry=https://registry.npm.taobao.org --disturl=https://npm.taobao.org/dist

---

I choosed taobao registry, I can't change anymore.

[yyx990803]

You can change it by editing ~/.vuerc.

Is that log all you get? Nothing else?

[vvpvvp]

I changed back to vue-cli, it's ok to init project.
And I reinstall @vue-cli, use vue create my-project command.


But it was still no go.

[vvpvvp]

I installed internal package global, but that does not work.

[yyx990803]

Should be an npm + windows issue: npm/npm#19032

[vvpvvp]

But I use mac, os x v10.11.6.

[zhengpq]

@vvpvvp
I have the same problem today, how did you solve it ?

[dnhyde]

Can you update vue-cli?
I have no issues with vue create my-project in version vue-cli-3.0.0-beta.11 + OSX 10.13.4.

You can check your version with vue -V and update vue-cli with
npm install -g @vue/cli or yarn global add @vue/cli

[zhengpq]

i am using the latest version of vue-cli , the version is 3.0.0-beta.11, it is the same with yours, i had tried to update vue-cli but did not work
@dnhyde

[dnhyde]

Ok, based on the error you posted on stackoverflow, it seems related to a plugin you are installing. I guess you already found this thread since you tried npm cache clean --force... I do not know how I can help, but could it be related to you npm version? I just noticed that I updated today to npm 6.1.0

[zhengpq]

i have updated my npm too, i also updated it to 6.1.0, but did not work , maybe i should try to reinstall the node.js, vue-cli and the npm , thank you for your help!

[zhengpq]

@dnhyde

i have updated my npm too, i also updated it to 6.1.0, but did not work , maybe i should try to reinstall the node.js, vue-cli and the npm , thank you for your help!

[kyleslight]

@zhengpq

According to this issue, cleaning npm cache hopefully helps the problem

[MartinYounghoonKim]

@vvpvvp
Did you solved this problem?

[vvpvvp]

@MartinYounghoonKim
Sadly, the problem still exists.