npm

作用: 模块管理(安装、卸载)

1) 全局安装 $npm install (i) xxx --global (-g)
2) 当前(本地)项目安装 $npm i xxx
把模块设置为开发依赖(开发中): $ npm i xxx --save-dev
把模块设置为生产依赖(部署到服务器):$ npm i xxx --save
安装在全局和本地的区别:
安装在全局后对任何项目都有作用(有可能版本冲突),但是只能基于命令的方式管理,不能基于commonjs的require导入使用(通俗说:不能导入到文件中基于代码来处理)$ npm root -g查看全局安装到的目录,在该目录下生成了一个xxx.cmd的文件(能用命令操作的原因)
安装在本地默认不能基于命令管理但是可以导入带文件中基于代码操作,只对当前项目有用。

在本地安装模块之前,最好先:$ npm init -y,生成package.json模块配置文件
package.json作用:
·把安装的mk生成配置清单,存放在package.json中,后期别人需要部署项 目时,只需要执行$npm i 就可以把所有的依赖项(包括开发和生产)重新 安装一遍“跑环境” $npm i --production只安装生产依赖模块
·可以基于scripts选项配置本地可执行的脚本命令 $npm run test
“scripts”: {
//test是命令,值是要做的事
“test”: “node xxx.js”
}
·在配置可执行脚本命令的时候,基于prosess的环境变量区分开发还是生产 环境
在这里插入图片描述

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、付费专栏及课程。

余额充值