Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/guide/local-cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,27 @@ overrides:

:::

::: warning Existing direct dependencies with npm
If your npm project already lists `vite` in `dependencies` or `devDependencies`, change that entry to the same alias as `overrides.vite`. npm requires a direct dependency and its override to use the [same dependency specification](https://docs.npmjs.com/cli/v11/configuring-npm/package-json/#overrides). Otherwise, `npm install` fails with `EOVERRIDE`.

For example, update an existing `vite` development dependency as follows. Keep the other dependencies in your manifest:

```json [package.json]
{
"devDependencies": {
"vite": "npm:@voidzero-dev/vite-plus-core@<vite-plus-version>",
"vite-plus": "<vite-plus-version>"
},
"overrides": {
"vite": "npm:@voidzero-dev/vite-plus-core@<vite-plus-version>",
"vitest": "<vitest-version>"
}
}
```

If you also declare `vitest` directly, set its dependency entry to the exact version in `overrides.vitest`. Run `npm install` after these changes to update the lockfile and installed dependencies.
:::

::: details Why are these settings needed?

Dependencies and plugins can import `vite` or `vitest` directly, even when your own code imports from `vite-plus`. These overrides align their dependencies with the toolchain Vite+ uses:
Expand Down
Loading