npm i 安装报错 (node 版本问题)

最新推荐文章于 2024-06-02 18:32:33 发布
最新推荐文章于 2024-06-02 18:32:33 发布
阅读量1.9w 收藏 8
点赞数 1
分类专栏： npm  问题集 文章标签： npm vue.js 前端
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/AJINNIU/article/details/122928383
版权 
PS D:\qieyin-main-frontend\huwen> npm i
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'upath@1.0.4',
npm WARN EBADENGINE   required: { node: '>=4 <=9' },
npm WARN EBADENGINE   current: { node: 'v14.18.3', npm: '8.3.1' }
npm WARN EBADENGINE }
npm WARN deprecated babel-preset-es2015@6.24.1: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated extract-text-webpack-plugin@2.1.2: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated html-webpack-plugin@2.30.1: out of support
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN tarball tarball data for file-saver@https://registry.npmjs.org/file-saver/-/file-saver-1.3.3.tgz (sha1-5oowx8sETi+zYrQoRp/rKRwuCdg=) seems to be corrupted. Trying again.
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over 
as this distribution is no longer supported and may contain bugs and critical security issues.   
npm WARN deprecated webpack-hot-middleware@2.22.0: Accidentally doesn't hot reload if warnings are seen
npm WARN deprecated mixin-deep@1.3.1: Critical bug fixed in v2.0.1, please upgrade to the latest 
version.
npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should 
use the URLSearchParams API instead.
npm WARN deprecated flatten@1.0.2: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated domelementtype@1.3.0: update to domelementtype@1.3.1
npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@4.2.1: this library is no longer supported
npm WARN deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated source-map-resolve@0.5.1: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN tarball tarball data for file-saver@https://registry.npmjs.org/file-saver/-/file-saver-1.3.3.tgz (sha1-5oowx8sETi+zYrQoRp/rKRwuCdg=) seems to be corrupted. Trying again.
npm WARN deprecated chokidar@2.0.3: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated uuid@3.2.1: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over 
as this distribution is no longer supported and may contain bugs and critical security issues.   
npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request@2.79.0: request has been deprecated, see https://github.com/request/rnpm WARN deprecated tar@2.2.1: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated axios@0.15.3: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated har-validator@2.0.6: this library is no longer supported
npm WARN deprecated bfj-node4@5.3.1: Switch to the `bfj` package for fixes and new features!     
npm WARN deprecated svgo@0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.     
npm WARN deprecated buffer@4.9.1: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated core-js@2.5.5: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your 
dependencies to the actual version of core-js.
npm ERR! code EINTEGRITY
npm ERR! sha1-5oowx8sETi+zYrQoRp/rKRwuCdg= integrity checksum failed when using sha1: wanted sha1-5oowx8sETi+zYrQoRp/rKRwuCdg= but got sha512-2lGfU4gymmhXRUiPLeQlnlkMaSY8azJB9W8e/vFp44AlAOEvzf6XiBUoTHO9NBM4OVlehybxDM9B4SwLBh42mw== sha1-zdTETTqiZOrC9o7BZbx5HDSvEjI=. (10271 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Admin\AppData\Local\npm-cache\_logs\2022-02-14T08_41_59_018Z-debug-0.log

会有一段

 这样的代码  required 是要求的node 版本   current 是 当前的配置 

根据需求改就可 然后 npm cache verify  清除缓存  npm i 安装  如果安装时失败 就使用cnpm i 安装

辛巴没有克
关注
  • 1
    点赞
  • 踩
  • 8
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
node 升级版本，vue报错 warn,及启动的error
前端小菜鸡的博客
02-17 1万+
error 或者warn 未截图，大概内容如下 1、npm install 安装依赖包时： EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'pkcs7@0.2.3', npm WARN EBADENGINE required: { node: '^0.10', npm: '^1.4.6' }, npm WARN EBADENGINE current: { node: 'v16.14.0', npm:
VUE 问题（1）
weixin_39223826的博客
06-02 2439
npm WARN EBADENGINE Unsupported engine { package: 'karma@1.7.1', npm WARN EBADENGINE required: { node: '0.10 || 0.12 || 4 || 5 || 6 || 7 || 8' }, npm WARN EBADENGINE current: { node: 'v11.15.0', npm: '7.14.0' } } npm ERR! code 1 npm ERR! path E:\works...
npm i 安装报错
南北极之间
03-07 1456
在工作中，我们可能同时在进行2个或者多个不同的项目开发，每个项目的需求不同，进而不同项目必须依赖不同版本的NodeJS运行环境，这种情况下，对于维护多个版本的node将会是一件非常麻烦的事情，nvm就是为解决这个问题而产生的，他可以方便的在同一台设备上进行多个node版本之间切换。Node.js平台，Node.js工具社区和Node.js库是快速移动的目标 - 在一个Node.js版本下可能有效的方法不能保证适用。比如node版本和node-sass的版本如果不对，就会报错。
gitee下载新的项目后npm install报错如下
最新发布
2301_77615930的博客
06-02 1433
gitee下载新的项目后npm install报错npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!
npm与node版本不匹配问题解决思路(一百五十八)
Android系统攻城狮
04-11 9148
npm与node版本不匹配问题解决思路
vue项目遇到的问题
qq_63096316的博客
04-16 1956
更新node-gyp:您正在使用的node-gyp版本(v3.8.0)非常旧，可能与您的Node.js版本(v16.0.0)不完全兼容。更新node-sass: node-sass包已弃用，取而代之的是sass。重新运行npm install:完成以上步骤后，在你的项目目录下重新运行npm install。解决：cmd 运行where python.exe，然后根据出现的地址重新set。1.从网上git下来后，运行时出现。2.重装node.js后运行出现。原因：node.js版本不匹配。
vue-element-admin Unsupported engine xxx required: { node: ‘8 || 10 || 12 || 14 || 16 || 17‘ }
极客星云-CSDN博客
01-03 4979
最近由于一些原因，从Mac OSX 迁移到 Windows 平台，在尝试运行基于vue-element-admin 项目时，发生了如下异常：vue-element-admin Unsupported engine xxx required: { node: '8 || 10 || 12 || 14 || 16 || 17' }
npm install报错
前端视听
05-14 347
在维护别人的项目的时候，在项目文件夹中安装npm install模块的时候，报错如下： npm ERR! path D:\ShopApp\node_modules\fsevents\node_modules\abbrev npm ERR! code ENOENT npm ERR! errno -4058 npm ERR! syscall access npm ERR! enoent ENOEN...
解决robotjs npm i 安装失败 node-modules 包 ， 包含 win7 及 win10以上的两个版本
10-09
总结来说，解决`npm i robotjs`在Windows系统上的安装问题，可以尝试手动复制预编译的`robotjs`文件到`node_modules`目录，这是一种快速且实用的解决方案，特别是对于遇到编译问题或网络问题的开发者。同时，确保你...
解决vue项目运行npm run serve报错的问题
01-18
最后去项目安装依赖 npm i 运行项目 npm run serve 如果这样子项目还是报同样的错误，那么就把node全局卸载，去控制面板卸载，然后安装，最后安装依赖，运行项目就可以成功了 补充知识：vue npm run serve报错Cannot...
npm install报错-vue-element-admin-fix-npm-problem-master.zip
01-02
在这个场景中，`vue-element-admin`是一个基于Vue.js的管理后台模板，而`npm i`是`npm install`的简写，同样用于安装项目依赖。`vue-element-admin-fix-npm-problem-master.zip`这个压缩包文件，显然包含了针对`vue-...
npm install 报错解决方法
04-25
有时npm本身可能存在bug，这时可以尝试更新npm到最新版本（`npm i -g npm`），或者回退到已知稳定的版本（如`npm i -g npm@5.x`）。 八、代理设置 如果你在使用代理网络环境下，需要设置npm的代理配置。可以使用`...
解决Window10系统下Node安装报错的问题分析
01-20
今天电脑重装了win10系统，在安装Node的过程中出现了下面的问题，下面就和大家分享下用来解决这种问题的小方法。 报错原因 随便问下度娘我们就可以知道，导致报错的原因是由于权限的关系，因此我们只需要使用管理员...
安装npm报错，安装淘宝镜像cnpm时出现问题及解决方案
qq_43628835的博客
10-29 9050
https://www.jianshu.com/p/3fd7d90db01a 感谢大佬，看了直接秒解决！！！
npm install 报错
编程语言与各种框架(Java,python)
08-30 2791
在package-lock.json文件中修改。在package.json可能需要添加属性 .npm install 报错。不支持nodejs 18 报错。
vue 前端框架构建踩坑记录（自用）
热门推荐
小康子的博客
07-15 1万+
进入前端模块根目录下执行构建命令： npm run build:prod 由于没有安装依赖包，所以提示如下： > osap-system-ui@4.4.0 build:prod > vue-cli-service build 'vue-cli-service' 不是内部或外部命令，也不是可运行的程序或批处理文件。 安装依赖： npm install 报错如下： npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve depen
npm install出现的问题
dongcao0的博客
02-21 1108
可以按照npm install提供的建议修改page.json对应中的版本，下面是错误例子。解决方式，找到node-ipc，降低或提高其版本号。如果还有，大概是版本不对应引起的。npm install较卡。
npm i出现报错npm ERR! code ENOENT
08-10
回答: 当npm出现ENOENT错误时，通常是由于找不到文件引起的。可能是路径不正确，需要确保在项目的根路径下运行命令，例如vue的启动命令一般是npm run dev / npm run serve，而react的启动命令是npm start。另外，也可能是因为安装的版本不匹配，可以尝试安装对应版本的插件。如果是安装其他包时出现错误，可能是安装的版本太高与当前项目不匹配。123 #### 引用[.reference_title] - *1* [Vue脚手架报错：npm ERR! code ENOENTnpm ERR! syscall opennpm ERR!](https://blog.csdn.net/weixin_56035334/article/details/125265069)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT0_1"}} ] [.reference_item] - *2* [【 npm ERR! code ENOENT npm ERR! syscall open npm ERR!项目运行报错问题】](https://blog.csdn.net/m0_45991266/article/details/131060804)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT0_1"}} ] [.reference_item] - *3* [npm install 报错(npm ERR! code EPERM npm ERR! syscall mkdir npm ERR! path D:\node.js\odejs)](https://blog.csdn.net/weixin_56661658/article/details/128512027)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT0_1"}} ] [.reference_item] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值