vite-plugin-terminal icon indicating copy to clipboard operation
vite-plugin-terminal copied to clipboard

Vite 3 support

Open sean-hill opened this issue 3 years ago • 2 comments

Hey! I'm trying to install this plugin with a project using Vite 3. But I'm getting this error when trying to install:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"^3.0.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^2.0.0" from [email protected]
npm ERR! node_modules/vite-plugin-terminal
npm ERR!   dev vite-plugin-terminal@"*" 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.

Looks like perhaps the peer dependency of vite needs to be updated?

sean-hill avatar Oct 25 '22 20:10 sean-hill

Encountering a similar issue installing on Vite 3.2 with pnpm

 WARN  Issues with peer dependencies found
.
└─┬ vite-plugin-terminal 1.0.2
  ├── ✕ unmet peer vite@^2.0.0: found 3.2.2
  └─┬ @rollup/plugin-strip 2.1.0
    ├── ✕ missing peer rollup@"^1.20.0 || ^2.0.0"
    └─┬ @rollup/pluginutils 3.1.0
      └── ✕ missing peer rollup@^1.20.0||^2.0.0
Peer dependencies that should be installed:
  rollup@">=1.20.0 <2.0.0 || >=2.0.0 <3.0.0"

Done in 1.5s

FossPrime avatar Nov 04 '22 07:11 FossPrime

Same

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"^3.1.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^2.0.0" from [email protected]
npm ERR! node_modules/vite-plugin-terminal
npm ERR!   dev vite-plugin-terminal@"*" 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.

doppiscantsleep avatar Nov 08 '22 19:11 doppiscantsleep