-
Notifications
You must be signed in to change notification settings - Fork 92
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
你好mac下npm install项目报错 #24
Comments
项目 没问题 我在我的电脑上运行成功了, macpro 10.14 Xcode10.2 , 按流程 用 yarn , 只是需要改几个路径 就 OK 了 |
你可以加入淘宝镜像试试; yarn config set registry https://registry.npm.taobao.org --global |
如果有部分电脑提示路径有问题,就把报错的路径改成相对路径;因为我配置了alias,可能有的电脑支持不太好;可以搜babel-plugin-module-resolver相关的文章了解一下具体用法。 |
我也遇到了这样的问题,多试几下,应该是网络问题。 |
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
Unhandled rejection Error: ENOSPC: no space left on device, write
npm ERR! code ERR_STREAM_DESTROYED
npm ERR! Cannot call write after a stream was destroyed
Unhandled rejection Error: ENOSPC: no space left on device, write
Unhandled rejection Error: ENOSPC: no space left on device, write
npm WARN registry Unexpected warning for https://registry.npm.taobao.org/: Miscellaneous Warning ENOSPC: ENOSPC: no space left on device, write
npm WARN registry Using stale package data from https://registry.npm.taobao.org/ due to a request error during revalidation.
Unhandled rejection Error: ENOSPC: no space left on device, write
Unhandled rejection Error: ENOSPC: no space left on device, write
Unhandled rejection Error: ENOSPC: no space left on device, write
npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0
The text was updated successfully, but these errors were encountered: