Mutliple warnings and deprecated dependencies on npm install vue/cli

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

[farreal]

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 🤘

[LinusBorg]

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

• Vue 3
• TS
• Babel
• router
• Vuex
• Jest
• Cypress
• eslint + prettier

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