npm

最新推荐文章于 2025-08-14 08:54:38 发布
最新推荐文章于 2025-08-14 08:54:38 发布
阅读量63 收藏
点赞数
CC 4.0 BY-SA版权
文章标签： json python
原文链接：https://my.oschina.net/huibaifa/blog/2990329

2019独角兽企业重金招聘Python工程师标准>>> hot3.png

1、查看所有高级的npm moudles

        npm list --depth=0

2、查看所有全局安装的模块

        npm list --depth=0 -global

3、删除全局模块

        npm uninstall -g <package>

4、删除本地模块

        npm uninstall 模块：删除模块，但不删除模块留在package.json中的对应信息

        npm uninstall 模块 --save：删除模块，同时删除模块留在package.json中dependencies下的对应信息

        npm uninstall 模块 --save-dev：删除模块，同时删除模块留在package.json中devDependencies下的对应信息

5、查看镜像得配置结果

        npm config get registry

6、设置淘宝镜像

        npm config set registry https://registry.npm.taobao.org
        npm config set disturl https://npm.taobao.org/dist

7、安装nrm源管理器

        npm install -g nrm

        查看可选源  nrm ls

        npm ---- https://registry.npmjs.org/

        cnpm --- http://r.cnpmjs.org/

        taobao - https://registry.npm.taobao.org/

        nj ----- https://registry.nodejitsu.com/

        rednpm - http://registry.mirror.cqupt.edu.cn/

        npmMirror  https://skimdb.npmjs.com/registry/

        edunpm - http://registry.enpmjs.org/

         带*为当前使用的源

         增加定制源

                nrm add registry 路径

        删除对应源

                nrm del <registry>

        切换对应源

                nrm use <registry>

        测试速度

                nrm test <registry>

注：

        dependencies依赖的包不仅开发环境能使用，生产环境也能使用

        devDependencies是只会在开发环境下依赖的模块

        通过NODE_ENV=development或NODE_ENV=production 指定开发还是生产环境。 

参考链接

    

转载于:https://my.oschina.net/huibaifa/blog/2990329

npm 安装指定版本（按版本安装）
日常笔记/总结/系列知识梳理
08-13 23万+
注解：比如， babel 是发布时，将 ES6 代码编译成 ES5 ，那么 babel 就是devDependencies。Vue项目中vue-router，由于发布之后还是依赖vue-router，所以是dependencies。
npm 超详细使用教程
我哎GIS博客
08-13 5734
npm，全名 node package manger。npm 是Node的开放式模块登记和管理系统，是Node.js包的标准发布平台，用于Node.js包的发布、传播、依赖控制，网址：https://www.npmjs.com/npm 提供了命令行工具，可以方便地下载、安装、升级、删除包，也可以让你作为开发者发布并维护包。在本文中，我们将深入探讨npm的各个方面，从安装到高级用法，帮助读者从入门到精通npm的使用。
国内npm源镜像（npm加速下载） 指定npm镜像
热门推荐
夜空孤狼啸的博客
06-29 33万+
国内npm源镜像（npm加速下载）指定npm镜像 nrm 是一个 npm 源管理器，允许你快速地在 npm 源间切换。
npm和cnpm（windows）安装步骤
09-14 16万+
一、什么是npm和cnpm npm（node package manager）：nodejs的包管理器，用于node插件管理（包括安装、卸载、管理依赖等）cnpm:因为npm安装插件是从国外服务器下载，受网络的影响比较大，可能会出现异常，如果npm的服务器在中国就好了，所以我们乐于分享的淘宝团队干了这事。来自官网：“这是一个完整 npmjs.org 镜像，你可以用此代替官方版本(只读)，同步频...............
npm下载
qq_37193169的博客
06-05 7882
下载地址：https://nodejs.cn/download/
npm详解
cyqzy的博客
06-26 5649
例如用淘宝源安装express模块：npm install express --registry=https://registry.npm.taobao.org。例如：全局安装淘宝npm镜像： npm install -g cnpm --registry=https://registry.npm.taobao.org。（4）阿里云npm源：https://registry.npm.alibaba-inc.com。（2）淘宝源：https://registry.npm.taobao.org。
npm报错：request to https://registry.npm.taobao.org failed, reason certificate has expired
maoge_666的博客
02-05 17万+
npm报错：request to https://registry.npm.taobao.org failed, reason certificate has expired
Npm使用教程
hong161688的博客
08-11 2万+
npm（Node Package Manager）是Node.js的包管理器，它允许开发者轻松地安装、更新、卸载和管理Node.js项目中的依赖包。npm是Node.js生态系统中不可或缺的一部分，极大地简化了项目依赖管理和代码共享的过程。本教程将详细介绍npm的安装、基础用法、高级功能以及常见问题解决方案。
npm 配置淘宝镜像
读心悦
10-12 7650
为了加速npm包的下载速度，尤其是在中国地区，配置淘宝的 npm 镜像（也称为cnpm镜像）是一个常见的方法。
npm切换镜像源
iynisxxr的博客
10-12 4684
切换npm国内镜像源
国内npm源镜像（npm加速下载）
07-10
国内镜像源，国内npm源镜像（npm加速下载）淘宝 NPM 镜像：https://registry.npm.taobao.org 阿里云 NPM 镜像：https://npm.aliyun.com 腾讯云 NPM 镜像：https://mirrors.cloud.tencent.com/npm/ 华为云 NPM 镜像：...
npm-exec:运行您的npm脚本，而无需加载所有npm
05-17
npm-exec 仅用于运行npm脚本的工具 3.1。 3.1.1。 3.1.2。 3.1.3。 3.1.4。 3.1.5。 1。 安装 $ npm install --save standalone-npm-exec 2。 用法 const npmExec = require ( 'npm-exec' ) ; npmExec (...
npmexclude:从 npm install 和 npm update 中排除模块
06-19
我制作这个工具是因为我假设npm install和npm update如果其中一个模块失败，则不会安装任何模块。 这个假设是不正确的； 显然我没有给予足够的重视。 我想如果您想抑制错误消息，这个工具仍然很有用，但重定向 ...
npm-windows-upgrade：在Windows上升级npm
02-03
在Windows上升级NPM 在Windows上升级npm需要手动步骤，以确保PowerShell / CMD找到新版本的npm。 这是一个用 :red_heart: 对于npm和Node，将过程简化为一个简单的命令。 用法 首先，通过从提升的PowerShell中运行...
【Datawhale夏令营】多模态RAG学习
米吉米粒的专栏
08-12 964
本文介绍了一个基于多模态检索增强生成（Multimodal RAG）的智能问答系统构建方案。该系统旨在处理PDF文档中的图文信息，通过PyMuPDF解析文本并构建知识库，采用向量检索与LLM生成相结合的问答流程。Baseline方案包含PDF解析、文本分块、向量化存储和检索生成等模块。通过提示词优化、输出格式标准化和温度参数调整等改进措施，系统评分从0.00346提升至0.1611。未来可优化分块策略、升级解析方案并加强多模态融合，以进一步提升系统性能。
Next.js 国际化：打造多语言应用
zimin的专栏
08-12 1185
Next.js 作为一个全栈 React 框架，在构建全球性应用时，国际化（Internationalization, i18n）是不可或缺的功能。国际化允许应用支持多种语言和区域设置，实现语言检测、内容翻译和路由本地化，提升用户体验并扩大受众范围。Next.js 通过灵活的配置和库支持，如 next-i18next 或内置的 i18n 功能，简化了多语言应用的开发。i18n 的核心包括语言检测（根据用户浏览器或首选项自动切换语言）、内容翻译（使用 JSON 文件或第三方服务）和路由本地化（如 /en/
package.json 的 overrides/resolutions 使用指南
cdq2012的博客
08-11 390
摘要：本文介绍了如何使用 pnpm 中的 resolutions 和 overrides 功能管理项目依赖，两者功能相同，overrides 是主要字段，resolutions 为兼容 Yarn 的别名。通过示例展示了全局重写、版本范围重写和嵌套依赖重写的语法，并列举了解决依赖冲突、修复安全漏洞、临时版本调整和指定内网地址等使用场景。注意事项包括优先级高于 dependencies、嵌套依赖仅影响一级以及缓存清理问题。合理使用这些功能可有效提升依赖管理的灵活性和项目稳定性。
npm删除包
最新发布
amy_jork的博客
08-14 103
在Vue项目中，如果你想要删除一个通过npm安装的包，可以使用npm或yarn这两种包管理工具来移除。
npm ERR! code ERR_STREAM_DESTROYED npm ERR! Cannot call write 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
### 解决 Windows 系统中 npm 运行时出现的 EPERM 和 ERR_STREAM_DESTROYED 问题 在使用 `vue-cli-service serve` 启动项目时，可能会因为权限不足（EPERM）或流被销毁（ERR_STREAM_DESTROYED）而遇到错误。以下是...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值