unmet peer vite@"^2.2.3 || ^3.0.0": found 4.0.0

[n8sabes]

Describe the bug

 WARN  Issues with peer dependencies found
.
├─┬ @vanilla-extract/vite-plugin 3.7.0
│ └── ✕ unmet peer vite@"^2.2.3 || ^3.0.0": found 4.0.0

Reproduction

vanilla-extract/packages/vite-plugin/package.json

Line 27 in 9312b66

"vite": "^2.2.3 || ^3.0.0"

System Info

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Memory: 73.55 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.0.1 - ~/.nvm/versions/node/v19.0.1/bin/node
    npm: 8.19.2 - ~/.nvm/versions/node/v19.0.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.98
    Firefox Developer Edition: 108.0
    Safari: 16.1

Used Package Manager

pnpm

Logs

No response

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[wmaurer]

I have the same problem using npm@8.19.2, which will error when installing @vanilla-extract/vite-plugin in a new project where vite@4.0.3 is being used (in this case using Nx and @nrwl/vite@15.4.0).

One can override the unmet dependency using:

npm install --save-dev @vanilla-extract/vite-plugin --legacy-peer-deps

From then on, all seems to work though, so my very simple test seems to show that this plugin is compatible with vite v4.

[maxlapides]

Here's another temporary solution: you can add this to your package.json:

"overrides": {
  "@vanilla-extract/vite-plugin": {
    "vite": "^4"
  }
}

[yuckiymouse]

Here's another temporary solution: you can add this to your package.json:

"overrides": {
  "@vanilla-extract/vite-plugin": {
    "vite": "^4"
  }
}

doesn't work, sadly.

[yuckiymouse]

I have the same problem using npm@8.19.2, which will error when installing @vanilla-extract/vite-plugin in a new project where vite@4.0.3 is being used (in this case using Nx and @nrwl/vite@15.4.0).

One can override the unmet dependency using:

npm install --save-dev @vanilla-extract/vite-plugin --legacy-peer-deps

From then on, all seems to work though, so my very simple test seems to show that this plugin is compatible with vite v4.

this works for me!

[askoufis]

Fixed in #949