簡體   English   中英

npm 不支持 Node.js v8.17.0

[英]npm does not support Node.js v8.17.0

所以我面臨的問題是我的package.json文件中的某些包需要大於10node版本。 所以我安裝了nvm package 來管理node版本,當我執行node -v時,它給了我這個: v12.19.0 因此,如果節點版本是12.19.0那么錯誤不應該出現,但我認為這是節點的全局版本,所以當我執行npm更新時,會出現以下情況:

npm WARN npm npm does not support Node.js v8.17.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm You can find the latest version at https://nodejs.org/
npm WARN EBADENGINE Unsupported engine { package: 'gulp-imagemin@7.1.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'imagemin-gifsicle@7.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'imagemin-jpegtran@7.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'imagemin-optipng@8.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'imagemin-pngquant@9.0.1',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'imagemin-svgo@8.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'yargs@16.2.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'gifsicle@5.1.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'execa@4.1.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'jpegtran-bin@5.0.2',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'optipng-bin@7.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'execa@4.1.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'ow@0.17.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'pngquant-bin@6.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'execa@4.1.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'y18n@5.0.5',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'yargs-parser@20.2.6',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN EBADENGINE Unsupported engine { package: 'wrap-ansi@7.0.0',
npm WARN EBADENGINE   required: { node: '>=10' },
npm WARN EBADENGINE   current: { node: 'v8.17.0', npm: '7.5.4' } }
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

added 165 packages, removed 190 packages, changed 69 packages, and audited 1485 packages in 2m

54 packages are looking for funding
  run `npm fund` for details

5 vulnerabilities (4 low, 1 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

出於某種原因,該應用程序使用的版本是 8.17.0。 我想將其更新為大於 10。我該怎么做?

我在Ubuntu 20.04上。

編輯

這是我的package.json文件:

{
    "name": "stash",
    "description": "Wordpress stack",
    "main": "index.js",
    "scripts": {
        "test": "echo \"Error: no test specified\" && exit 1"
    },
    "repository": {
        "type": "git",
        "url": "git@gitlab.com:undefinedio/stash.git"
    },
    "author": "Vincent Peters",
    "devDependencies": {
        "babel-polyfill": "^6.23.0",
        "babel-preset-es2015": "^6.24.1",
        "babelify": "^7.3.0",
        "browser-sync": "^2.26.14",
        "browserify": "^14.4.0",
        "buffer": "^5.0.6",
        "dotenv": "^4.0.0",
        "gulp": "^4.0.2",
        "gulp-autoprefixer": "^4.0.0",
        "gulp-clean-css": "^3.7.0",
        "gulp-composer": "^0.4.0",
        "gulp-concat": "^2.6.1",
        "gulp-consolidate": "^0.2.0",
        "gulp-debug": "^3.1.0",
        "gulp-filter": "^5.0.0",
        "gulp-header": "^1.8.9",
        "gulp-iconfont": "^10.0.3",
        "gulp-if": "^2.0.2",
        "gulp-imagemin": "^7.1.0",
        "gulp-load-plugins": "^1.5.0",
        "gulp-notify": "^3.0.0",
        "gulp-plumber": "^1.1.0",
        "gulp-sass": "^3.1.0",
        "gulp-sourcemaps": "^2.6.0",
        "gulp-streamify": "^1.0.2",
        "gulp-uglify": "^3.0.0",
        "gulp-util": "^3.0.8",
        "gulp-watch": "^5.0.1",
        "imagemin-gifsicle": "^7.0.0",
        "imagemin-jpegtran": "^7.0.0",
        "imagemin-optipng": "^8.0.0",
        "imagemin-pngquant": "^9.0.1",
        "imagemin-svgo": "^8.0.0",
        "main-bower-files": "^2.13.1",
        "merge-stream": "^1.0.1",
        "node-bourbon": "^4.2.8",
        "node-neat": "^2.0.0-beta.0",
        "susy": "^2",
        "vinyl-buffer": "^1.0.0",
        "vinyl-source-stream": "^1.1.0",
        "yargs": "^16.2.0"
    },
    "dependencies": {
        "flickity": "^2.2.2",
        "flickity-imagesloaded": "^2.0.0",
        "gsap": "^1.20.2",
        "lazysizes": "^5.3.0",
        "scrollmagic": "^2.0.5",
        "viewport-units-buggyfill": "^0.6.2"
    }
}    },
    "dependencies": {
        "flickity": "^2.2.2",
        "flickity-imagesloaded": "^2.0.0",
        "gsap": "^1.20.2",
        "lazysizes": "^5.3.0",
        "scrollmagic": "^2.0.5",
        "viewport-units-buggyfill": "^0.6.2"
    }
}

看來當前安裝的npm與新節點不兼容。

解決方案是卸載 npm,然后重新安裝將包含正確版本的 npm 的節點。

就是這樣:

  1. 卸載 npm。

    Mac:須藤 npm 卸載 -g npm

    Windows:npm卸載-g npm

  2. https://nodejs.org安裝節點

我相信問題在於您的package.json只需運行npm install ,它應該可以工作。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM