请求大佬帮忙解决一下vue脚本架安装有问题

最新推荐文章于 2024-03-12 10:50:18 发布

Aurora_c77

最新推荐文章于 2024-03-12 10:50:18 发布

阅读量942

点赞数

文章标签： vue.js javascript npm

本文链接：https://blog.csdn.net/Aurora_c77/article/details/127170641

版权

在win+r中输入cmd然后查看环境发现vue脚本架下载有问题

C:\Users\cqq>node -v
v14.15.3

C:\Users\cqq>npm install -g @vue/cli
npm WARN invalid config registry=""
npm WARN invalid config Must be a full url with 'http://'
npm WARN invalid config registry=""
npm WARN invalid config Must be a full url with 'http://'
npm WARN deprecated subscriptions-transport-ws@0.11.0: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://npm.community>

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\cqq\AppData\Roaming\npm-cache\_logs\2022-10-05T02_39_30_836Z-debug.log

C:\Users\cqq>npm config set registry https://registry.npm.taobao.org
npm WARN invalid config registry=""
npm WARN invalid config Must be a full url with 'http://'
npm WARN invalid config registry=""
npm WARN invalid config Must be a full url with 'http://'

C:\Users\cqq>vue -V
'vue' 不是内部或外部命令，也不是可运行的程序
或批处理文件。

C:\Users\cqq>node -v
v14.15.3

C:\Users\cqq>vue -V
'vue' 不是内部或外部命令，也不是可运行的程序
或批处理文件。

C:\Users\cqq> npm install -g @vue/cli --registry https://reg
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://reg/@vue%2fcli failed, reason: getaddrinfo ENOTFOUND reg
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\cqq\AppData\Roaming\npm-cache\_logs\2022-10-05T02_43_04_504Z-debug.log