search

vuejs / vue-cli

🛠️ webpack-based tooling for Vue.js Development
https://cli.vuejs.org/
MIT License
29.75k stars 6.33k forks source link

Mutliple warnings and deprecated dependencies on npm install vue/cli #5690

Open dorian-yeager opened 4 years ago

dorian-yeager commented 4 years ago

Version

4.4.6

Reproduction link

https://github.com/oci-labs/rapid-stack/blob/master/vue_apps/vue_app/dockerfile

Environment info

  System:
    OS: Linux 5.4 Alpine Linux
    CPU: (1) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 14.5.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0 
    @vue/babel-plugin-transform-vue-jsx:  1.0.0 
    @vue/babel-preset-app:  3.11.0 
    @vue/babel-preset-jsx:  1.1.0 
    @vue/babel-sugar-functional-vue:  1.0.0 
    @vue/babel-sugar-inject-h:  1.0.0 
    @vue/babel-sugar-v-model:  1.0.0 
    @vue/babel-sugar-v-on:  1.1.0 
    @vue/cli-overlay:  3.11.0 
    @vue/cli-plugin-babel: ^3.11.0 => 3.11.0 
    @vue/cli-service: ^3.11.0 => 3.11.0 
    @vue/cli-shared-utils:  3.11.0 
    @vue/component-compiler-utils:  3.0.0 
    @vue/preload-webpack-plugin:  1.1.1 
    @vue/web-component-wrapper:  1.2.0 
    vue: ^2.6.10 => 2.6.10 
    vue-hot-reload-api:  2.3.4 
    vue-loader:  15.7.1 
    vue-router: ^3.0.3 => 3.1.3 
    vue-style-loader:  4.1.2 
    vue-template-compiler: ^2.6.10 => 2.6.10 
    vue-template-es2015-compiler:  1.9.1 
  npmGlobalPackages:
    @vue/cli: 4.4.6

Steps to reproduce

npm i -g @vue/cli

What is expected?

ok

What is actually happening?

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated @hapi/joi@15.1.1: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/address@2.1.4: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14 . Upgrade to chokidar 3 with 15x less dependencies. 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 checkPermissions Missing write access to /usr/local/lib npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/@vue/cli/node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

I run into this bug when installing vue-cli

shirshak55 commented 4 years ago

Why so many warning lol. See these warning when i use yarn . And this comes when i install other packages .

warning "@vue/cli > @babel/preset-env@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/helper-compilation-targets@7.10.4" has unmet peer dependency "@babel/core@^7.0.0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-async-generator-functions@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-class-properties@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-dynamic-import@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-json-strings@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-nullish-coalescing-operator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-numeric-separator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-object-rest-spread@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-optional-catch-binding@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-optional-chaining@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-private-methods@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-unicode-property-regex@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-async-generators@7.8.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-class-properties@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-dynamic-import@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-json-strings@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-nullish-coalescing-operator@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-numeric-separator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-object-rest-spread@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-optional-catch-binding@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-optional-chaining@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-syntax-top-level-await@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-arrow-functions@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-async-to-generator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-block-scoped-functions@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-block-scoping@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-classes@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-computed-properties@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-destructuring@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-dotall-regex@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-duplicate-keys@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-exponentiation-operator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-for-of@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-function-name@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-literals@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-member-expression-literals@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-modules-amd@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-modules-commonjs@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-modules-systemjs@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-modules-umd@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-named-capturing-groups-regex@7.10.4" has unmet peer dependency "@babel/core@^7.0.0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-new-target@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-object-super@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-parameters@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-property-literals@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-regenerator@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-reserved-words@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-shorthand-properties@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-spread@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-sticky-regex@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-template-literals@7.10.5" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-typeof-symbol@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-unicode-escapes@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-transform-unicode-regex@7.10.4" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/preset-modules@0.1.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-class-properties > @babel/helper-create-class-features-plugin@7.10.5" has unmet peer dependency "@babel/core@^7.0.0".
warning "@vue/cli > @babel/preset-env > @babel/plugin-proposal-unicode-property-regex > @babel/helper-create-regexp-features-plugin@7.10.4" has unmet peer dependency "@babel/core@^7.0.0".
MrGRA commented 4 years ago

I have the same warnings.

macOS version: Catalina 10.15.6 npm version: 6.14.7 node version: v14.8.0

~/S/tests ❯❯❯ npm install -g @vue/cli

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
/usr/local/bin/vue -> /usr/local/lib/node_modules/@vue/cli/bin/vue.js

> fsevents@1.2.13 install /usr/local/lib/node_modules/@vue/cli/node_modules/fsevents
> node install.js

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node

> @apollo/protobufjs@1.0.5 postinstall /usr/local/lib/node_modules/@vue/cli/node_modules/@apollo/protobufjs
> node scripts/postinstall

> core-js@3.6.5 postinstall /usr/local/lib/node_modules/@vue/cli/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
> https://opencollective.com/core-js 
> https://www.patreon.com/zloirock 

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

npm WARN @vue/compiler-sfc@3.0.0-rc.5 requires a peer of vue@3.0.0-rc.5 but none is installed. You must install peer dependencies yourself.

+ @vue/cli@4.5.3
added 252 packages from 148 contributors, removed 129 packages, updated 269 packages and moved 6 packages in 45.137s

And it fails using the default options

~/S/tests ❯❯❯ vue create someapp

Vue CLI v4.5.3
Failed to check for updates
✨  Creating project in /Users/guilhermealmeida/Sites/tests/someapp.
🗃  Initializing git repository...
⚙️  Installing CLI plugins. This might take a while...

 ERROR  Error: spawn yarn ENOENT
Error: spawn yarn ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
    at onErrorNT (internal/child_process.js:468:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
~/S/tests ❯❯❯
PLQin commented 4 years ago

I also noticed the problem and it would be nice to get an official explanation

Bibi10 commented 3 years ago

I used >yarn global add @vue/cli instead of npm i -g @vue/cli and it worked well.

wokes commented 3 years ago

First you need to uninstall old vue-cli with npm uninstall vue-cli -g, then proceed to npm install -g @vue/cli

gitDylanHub commented 3 years ago

I've tried uninstalling and reinstalling, made sure I am on the latest node and npm still getting the error with the peer dep missing for Vue 3. However, installing Vue 3 doesn't fix the issue either.

Mac UserBlah/.nvm/versions/node/v13.9.0/lib ├── @vue/cli@4.5.6 ├── bower@1.8.8 ├── eslint@6.8.0 ├── grunt-cli@1.3.2 ├── json-server@0.16.1 ├── ls@0.2.1 ├── npm@6.14.8 ├── phs-ui@0.3.10 -> /Users/dywright/dev/ui/phs-ui └── typescript@4.0.3

npm ERR! peer dep missing: vue@3.0.0, required by @vue/compiler-sfc@3.0.0

ghost commented 3 years ago

I had a similar issue. I used the following commands to firstly update the version of npm I was using, uninstalling older versions of vue cli and re-installing the latest vue cli.

npm install -g npm npm uninstall vue-cli -g npm i -g @vue/cli

These steps seemed to work for me. Hope its helpful to others with this issue 🤘

kendallroden commented 3 years ago

The above didn't work from me- I get a ton of deprecation warnings on Mac using yarn and npm respectively.. is there any real guidance here on this issue?

macOS Catalina version 10.15.6 node version v14.13.0 npm version 6.14.8

npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated @hapi/joi@15.1.1: joi is leaving the @hapi organization and moving back to 'joi' (https://github.com/sideway/joi/issues/2411) npm WARN deprecated @hapi/address@2.1.4: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. 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 @vue/compiler-sfc@3.0.0 requires a peer of vue@3.0.0 but none is installed. You must install peer dependencies yourself.

terrygreen0606 commented 3 years ago

This vue cli is really weird. Tried to find the answer here #2862, but with no success.

Peggy535 commented 3 years ago

Hi all

Had the same problem today too, but think I've managed to solve it.

Currently running: -macOS Catalina 10.15.7 -node.js 14.13.1 -npm 6.14.8

I'm also using oh-my-zsh in my terminal.

I had to do the following having found a previous post.

Working directory: /Users/Peggy

1) I completely removed node and npm. To do this I followed: https://www.positronx.io/how-to-uninstall-node-js-and-npm-from-macos/

2) Then I downloaded the macOS node/npm package and installed this.

3) Once installed, I used the command 'sudo npm install -g @vue/cli' and received the following output:

➜ / sudo npm install -g @vue/cli npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142 npm WARN deprecated @hapi/joi@15.1.1: joi is leaving the @Hapi organization and moving back to 'joi' (sideway/joi#2411) npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/address@2.1.4: This version has been deprecated and is no longer supported or maintained npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. File Paths for Vue and Vue-CLI /Users/peggy/.npm-packages/bin/vue -> /Users/peggy/.npm-packages/lib/node_modules/@vue/cli/bin/vue.js

npm WARN @vue/compiler-sfc@3.0.0 requires a peer of vue@3.0.0 but none is installed. You must install peer dependencies yourself.

4) Do an echo $PATH. Check that the file paths for both Vue and Vue-CLI are within your $PATH variable. If Vue and Vue-CLI load correctly the file path's will be given as above highlighted *****

If not, as was the case for me I simply did: export PATH=$PATH:/Users/peggy/.npm-packages/bin (AND) export PATH=$PATH:/Users/peggy/.npm-packages/lib/node_modules/@vue/cli/bin

5) Punch the air and allow the smile to happen.

dargmuesli commented 3 years ago

Many warnings should be fixed with https://github.com/vuejs/vue-cli/pull/5973.

zjivkas commented 3 years ago

On windows 10 I first tried with npm i -g @vue/cli - but it was reproducing the same error which of course prevented use of vue CLI : npm WARN @vue/compiler-sfc@3.0.0 requires a peer of vue@3.0.0 but none is installed. You must install peer dependencies yourself.

However, using yarn instead of npm worked for me. yarn global add @vue/cli

Recently npm has release (https://www.npmjs.com/package/@vue/compiler-sfc) with hopefully a fix via npm: npm i @vue/compiler-sfc

ndrslmpk commented 3 years ago

Similar problem on my side...

npm WARN notsup Unsupported engine for graphql@15.4.0: wanted: {"node":">= 10.x"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: graphql@15.4.0 npm WARN notsup Unsupported engine for object-path@0.11.5: wanted: {"node":">= 10.12.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: object-path@0.11.5 npm WARN notsup Unsupported engine for execa@3.4.0: wanted: {"node":"^8.12.0 || >=9.7.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: execa@3.4.0 npm WARN notsup Unsupported engine for human-signals@1.1.1: wanted: {"node":">=8.12.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: human-signals@1.1.1 npm WARN notsup Unsupported engine for execa@3.4.0: wanted: {"node":"^8.12.0 || >=9.7.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: execa@3.4.0 npm WARN notsup Unsupported engine for mkdirp@1.0.4: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: mkdirp@1.0.4 npm WARN notsup Unsupported engine for semver@7.3.2: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: semver@7.3.2 npm WARN notsup Unsupported engine for globby@11.0.1: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: globby@11.0.1 npm WARN notsup Unsupported engine for clean-stack@3.0.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: clean-stack@3.0.0 npm WARN notsup Unsupported engine for fs-extra@9.0.1: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: fs-extra@9.0.1 npm WARN notsup Unsupported engine for wrap-ansi@7.0.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: wrap-ansi@7.0.0 npm WARN notsup Unsupported engine for escape-string-regexp@4.0.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: escape-string-regexp@4.0.0 npm WARN notsup Unsupported engine for universalify@1.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@1.0.0 npm WARN notsup Unsupported engine for universalify@2.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@2.0.0 npm WARN notsup Unsupported engine for chalk@4.1.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: chalk@4.1.0 npm WARN notsup Unsupported engine for clean-stack@3.0.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: clean-stack@3.0.0 npm WARN notsup Unsupported engine for fs-extra@9.0.1: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: fs-extra@9.0.1 npm WARN notsup Unsupported engine for semver@7.3.2: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: semver@7.3.2 npm WARN notsup Unsupported engine for object-treeify@1.1.29: wanted: {"node":">= 10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: object-treeify@1.1.29 npm WARN notsup Unsupported engine for escape-string-regexp@4.0.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: escape-string-regexp@4.0.0 npm WARN notsup Unsupported engine for universalify@1.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@1.0.0 npm WARN notsup Unsupported engine for universalify@2.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@2.0.0 npm WARN notsup Unsupported engine for fs-extra@9.0.1: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: fs-extra@9.0.1 npm WARN notsup Unsupported engine for semver@7.3.2: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: semver@7.3.2 npm WARN notsup Unsupported engine for universalify@1.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@1.0.0 npm WARN notsup Unsupported engine for universalify@2.0.0: wanted: {"node":">= 10.0.0"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: universalify@2.0.0 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\@vue\cli\node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN notsup Unsupported engine for chalk@4.1.0: wanted: {"node":">=10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: chalk@4.1.0 npm WARN notsup Unsupported engine for cli-width@3.0.0: wanted: {"node":">= 10"} (current: {"node":"8.11.1","npm":"6.14.8"}) npm WARN notsup Not compatible with your version of node/npm: cli-width@3.0.0 npm WARN @vue/compiler-sfc@3.0.2 requires a peer of vue@3.0.2 but none is installed. You must install peer dependencies yourself.

  • @vue/cli@4.5.8 updated 1 package in 32.628s

although i used npm i @vue/compiler-sfc in advance and give the following npm packages

+-- @vue/compiler-sfc@3.0.2 +-- core-js@3.7.0 +-- keypress@0.2.1 +-- npm-check@5.9.2 +-- oled-js@4.0.5 +-- socket.io@2.1.1 `-- vue@3.0.2

tonalmathew commented 3 years ago

Hi all, Had the same error, I got it fixed by the following commands: npm install -g npm npm uninstall vue-cli -g npm i -g @vue/cli

dearzubi commented 3 years ago

I had a similar issue. I used the following commands to firstly update the version of npm I was using, uninstalling older versions of vue cli and re-installing the latest vue cli.

npm install -g npm npm uninstall vue-cli -g npm i -g @vue/cli

These steps seemed to work for me. Hope its helpful to others with this issue 🤘

Thanks worked for me

sebastianhaberey commented 3 years ago

I am not sure all of the symptoms posted here are related. I am getting the same deprecation warnings as OP @dorian-yeager and @kendallroden and @Peggy535 regarding outdated hapi / chokidar / fsevents / har-validator dependencies.

I don't believe theses warnings can be solved by installing / uninstalling vue-cli or anything else. They simply mean the maintainer needs to update the package's dependencies to more recent versions. So our best chance is for @dargmuesli #5973 changes to be released.

jhulyacosta commented 3 years ago

Hi all, Had the same error, I got it fixed by the following commands: npm install -g npm npm uninstall vue-cli -g npm i -g @vue/cli

Thanks worked for me

diadras commented 3 years ago

Updating NPM and reinstalling Vue does not work. I kind of expected this since I started using it since a few days ago. Seems like the maintainer needs to update the packages. I hope this won't cause any large issues in the future :) I really like Vue so far.

mathiasselleslach commented 3 years ago

Same here. Sad, after all this time...is there any update to be expected?

LinusBorg commented 3 years ago

I'd like to clarify that we cannot upgrade transitive dependencies of packages that we are using. Even if we update our direct dependencies, we cannot ensure that these dependencies won't themselves still depend on deprecated packages.

I'd also like to clarify that, while annoying, these warnings don't necessarily mean that these transitive dependencies will have any effect on your app. They could, i.e., be devDependencies of a package used by a package use by a package used by vue-cli, and yet, that nested, deprecated dependency will never be required at any step of using vue-cli.

Similarly, peer Dependency warnings are also often a side effect of the install process itself or transitive dependencies, but usually not something we can resolve or something affecting your code.

In other words: While we can improve the situation for our direct dependencies in many situations, and usually do (i.e. #5973 mentioned above was merged back in Oct. 2020), we can't resolve warnings like these for transitive dependencies, so you will have to live with them in some scenarios.

That's part of the JS package ecosystem.

Also, @mathiasselleslach please tell me which warnings you got, specifically. I just now installed a new project with

and all I got were 0 deprecation warnings and 6 peerDependency warnings, which are unavoidable due to the npm install process - and most of these are just "misfires". Example:

warning "@vue/cli-plugin-unit-jest > vue-jest@3.0.7" has incorrect peer dependency "vue@^2.x".
warning "@vue/cli-plugin-unit-jest > vue-jest@3.0.7" has unmet peer dependency "vue-template-compiler@^2.x".
warning " > sass-loader@8.0.2" has unmet peer dependency "webpack@^4.36.0 || ^5.0.0".
warning " > vue-jest@5.0.0-alpha.8" has unmet peer dependency "@babel/core@7.x".
warning " > vue-jest@5.0.0-alpha.8" has unmet peer dependency "babel-jest@>= 24 < 27".
warning " > vue-jest@5.0.0-alpha.8" has unmet peer dependency "jest@>= 24 < 27 ".

See that warning about a missing peer dep for "webpack"? We have webpck 4.46 installed and yet, yarn/npm complain. Why? because webpack is a dependency of @vue/cli-service, and therefore not listed in your project's package.json. But it's there and everything it working. Same goes for jest, babel-jest and @babel/core

Abdelbar-Terbachi commented 3 years ago

3. sudo npm install -g @vue/cli

think you very much sir

Abdelbar-Terbachi commented 3 years ago

thank

Waqar-Ahmad-webdev commented 2 years ago

I am facing a weird problem with vue/cli, I have installed it via npm, but no yarn installed in my machine yet, and when I create a project with vue "vue create project-name" and finally it ended up with the following error: Screenshot_20211216-164047

currently running: ubuntu 16.04 memory: 15.6GiB processor: Intel® Core™ i7 CPU Q 720 @ 1.60GHz × 8 OS type: 64-bit

But I, eventually, installed yarn globally then I enter "yarn serve " and it ends up with no errors, any more. What is this? Not working with npm but working with yarn!!!!! Any Suggestions would be helpful.

yuri-un commented 2 years ago

@dorian-yeager Two options:

The second one worked for me. The VS Code Terminal can throw these kind of errors, while other Command tools may work OK.

dorian-yeager commented 2 years ago

All,

In the last 24 hours I upgraded the project to use Vue3 and Vite. I will be merging this code shortly. Once this is done all errors related to vue-cli are gone because it is abandoned for Vite and the superior create-vue command. I appreciate your work and patience.

On Tue, Feb 15, 2022 at 6:46 AM yuri-un @.***> wrote:

@dorian-yeager https://github.com/dorian-yeager Two options:

  • reinstall the tools;
  • try to fix the PATH pointers to your node.js and npm folders or executables.

The second one worked for me. The VS Code Terminal can throw these kind of errors, while other Command tools may work OK.

— Reply to this email directly, view it on GitHub https://github.com/vuejs/vue-cli/issues/5690#issuecomment-1040231080, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIU7VI7I2QTJQPTDAECTECDU3JDKLANCNFSM4O3BDOWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

toastoaster commented 2 years ago

Unfortunately I still get these errors with a freshly installed Nodejs:

PS > npm i -g @vue/cli
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated apollo-tracing@0.15.0: The `apollo-tracing` package is no longer part of Apollo Server 3. See https://www.apollographql.com/docs/apollo-server/migration/#tracing for details
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated graphql-extensions@0.15.0: The `graphql-extensions` API has been removed from Apollo Server 3. Use the plugin API instead: https://www.apollographql.com/docs/apollo-server/integrations/plugins/
npm WARN deprecated apollo-cache-control@0.14.0: The functionality provided by the `apollo-cache-control` package is built in to `apollo-server-core` starting with Apollo Server 3. See https://www.apollographql.com/docs/apollo-server/migration/#cachecontrol for details.
npm WARN deprecated uuid@3.4.0: 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 subscriptions-transport-ws@0.9.19: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws    For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
npm WARN deprecated graphql-tools@4.0.8: This package has been deprecated and now it only exports makeExecutableSchema.\nAnd it will no longer receive updates.\nWe recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc.\nCheck out https://www.graphql-tools.com to learn what package you should use instead
TusharRoy23 commented 1 year ago

And this is my warning. Does anyone have any updates? 

npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

Node: 18.16.1 Vue: 2.7.7

Swathimygapula commented 4 months ago

How do i solve this?

up to date in 396ms PS C:\Users\swath\OneDrive\Desktop> npm i -g @vue/cli npm WARN deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm WARN deprecated @babel/plugin-proposal-nullish-coalescing-operator@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead. npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated @babel/plugin-proposal-optional-chaining@7.21.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated apollo-datasource@3.3.2: The apollo-datasource package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated apollo-server-errors@3.3.1: The apollo-server-errors package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated apollo-server-plugin-base@3.7.2: The apollo-server-plugin-base package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated apollo-server-types@3.8.0: The apollo-server-types package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated shortid@2.2.16: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated apollo-reporting-protobuf@3.4.0: The apollo-reporting-protobuf package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/usage-reporting-protobuf package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated apollo-server-env@4.2.1: The apollo-server-env package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/utils.fetcher package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm WARN deprecated subscriptions-transport-ws@0.11.0: The subscriptions-transport-ws package is no longer maintained. We recommend you use graphql-ws instead. For help migrating Apollo software to graphql-ws, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws For general help using graphql-ws, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md npm WARN deprecated vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.