Skip to content

npm install twice error #463

@wxfred

Description

@wxfred

Describe the bug

Run npm install video.js @videojs-player/vue --save
Then run npm install, the error comes out

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @videojs-player/vue@1.0.0
npm ERR! Found: video.js@8.10.0
npm ERR! node_modules/video.js
npm ERR!   video.js@"^8.10.0" from the root project
npm ERR!   video.js@"^7 || ^8" from @videojs/http-streaming@3.10.0
npm ERR!   node_modules/@videojs/http-streaming
npm ERR!     @videojs/http-streaming@"3.10.0" from video.js@8.10.0
npm ERR!   1 more (videojs-contrib-quality-levels)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer video.js@"7.x" from @videojs-player/vue@1.0.0
npm ERR! node_modules/@videojs-player/vue
npm ERR!   @videojs-player/vue@"^1.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: video.js@7.21.5
npm ERR! node_modules/video.js
npm ERR!   peer video.js@"7.x" from @videojs-player/vue@1.0.0
npm ERR!   node_modules/@videojs-player/vue
npm ERR!     @videojs-player/vue@"^1.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Reproduction

Run npm install video.js @videojs-player/vue --save
Then run npm install, the error comes out

System Info

System:
  OS: Windows 10 10.0.19045
  CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
  Memory: 14.61 GB / 31.84 GB
Binaries:
  Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
  npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Chrome: 123.0.6312.122
npmPackages:
  @videojs-player/vue: ^1.0.0 => 1.0.0
  video.js: ^8.10.0 => 8.10.0

Used Package Manager

npm

Validations

  • Read the the documentation in detail.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
  • The provided reproduction is a minimal reproducible example of the bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions