npm

转自: http://www.cnblogs.com/linjiqin/p/3765772.html

npm是一个包管理和分发的工具,已经成为了非官方的发布node模块(包)的标准。有了npm,可以很快的找到特定服务要使用的包,进行下载、安装以及管理已经安装的包。

更多命令请参看npm官方文档:https://www.npmjs.org/doc/


package.json 文件可以为npm提供包的依赖关系配置, 从而开始下载依赖, 在同目录下会出现一个用来存放各种包的node_modules文件夹.  

如图:


package文件具体参数, 参考链接: http://www.mujiang.info/translation/npmjs/files/package.json.html


node的安装分为全局模式和本地模式。


一般情况下会以本地模式运行,包会被安装到和你的应用程序代码的本地node_modules目录下。

命令:  npm install moduleNames


在全局模式下,Node包会被安装到Node的安装目录下的node_modules下。

命令:  $npm install  moduleName -g


使用$npm set global=true来设定安装模式,$npm get global可以查看当前使用的安装模式。


代码中,直接通过require()的方式是没有办法调用全局安装的包的。

全局的安装是供命令行使用的,就好像全局安装了vmarket后,就可以在命令行中直接运行vm命令


npm install <name> --save

安装的同时,将信息写入package.json中项目路径中

如果有package.json文件时,直接使用npm install方法就可以根据dependencies配置安装所有的依赖包,这样代码提交到github时,就不用提交node_modules这个文件夹了。

npm view moduleNames:查看node模块的package.json文件夹
注意事项:如果想要查看package.json文件夹下某个标签的内容,可以使用$npm view moduleName labelName

npm list:查看当前目录下已安装的node包
注意事项:Node模块搜索是从代码执行的当前目录开始的,搜索结果取决于当前使用的目录中的node_modules下的内容。$ npm list parseable=true可以目录的形式来展现当前安装的所有node包


npm view moudleName dependencies:查看包的依赖关系

npm view moduleName repository.url:查看包的源文件地址

npm view moduleName engines:查看包所依赖的Node的版本


npm help folders:查看npm使用的所有文件夹

npm rebuild moduleName:用于更改包内容后进行重建

npm outdated:检查包是否已经过时,此命令会列出所有已经过时的包,可以及时进行包的更新

npm update moduleName:更新node模块

npm uninstall moudleName:卸载node模块


$ npm help json  访问npm的json文件夹
此命令会以默认的方式打开一个网页,如果更改了默认打开程序则可能不会以网页的形式打开。


$ npm search packageName  发布一个npm包的时候,需要检验某个包名是否已存在


npm init:会引导你创建一个package.json文件,包括名称、版本、作者这些信息等

npm -v:查看npm安装的版本


npm remove <name>移除

npm update <name>更新

npm ls 列出当前安装的了所有包

npm root 查看当前的安装路径

npm root -g  查看全局的包的安装路径

npm help  帮助,如果要单独查看install命令的帮助,可以使用的npm help install


https://npmjs.org/doc/


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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb2d693d npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb2d693d npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb2d693d'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb2d693d' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\a4a16f53 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\a4a16f53'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\a4a16f53' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\a4a16f53' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EPERM: EPERM: operation not permitted, open 'D:\\Node\\node_cache\\_cacache\\tmp\\6ee0a780' npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation. 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\aa34d15e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\dd6cc8ed npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\df92457e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\dd6cc8ed npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\dd6cc8ed'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\dd6cc8ed' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\01bdab06 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\eb849235 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\eb849235'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb849235' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\eb849235' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\df92457e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\df92457e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\df92457e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\3688e03a npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\35daa67e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 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 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 npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write after a stream was destroyed npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\35daa67e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\35daa67e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\35daa67e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\01bdab06 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\01bdab06'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\01bdab06' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! code EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\884bfc72 npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\884bfc72'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\884bfc72' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\884bfc72' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\aa34d15e npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\aa34d15e'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\aa34d15e' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. 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 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 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 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 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 EPERM npm ERR! syscall open npm ERR! path D:\Node\node_cache\_cacache\tmp\3688e03a npm ERR! errno -4048 npm ERR! Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a' npm ERR! [OperationalError: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! cause: [Error: EPERM: operation not permitted, open 'D:\Node\node_cache\_cacache\tmp\3688e03a'] { npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! }, npm ERR! isOperational: true, npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'open', npm ERR! path: 'D:\\Node\\node_cache\\_cacache\\tmp\\3688e03a' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator.
05-16
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值