Replies: 1 comment
-
|
add "pnpm": {
"overrides": {
"vite": "npm:@voidzero-dev/vite-plus-core@latest"
},
"peerDependencyRules": {
"allowAny": ["vite"]
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
{ "devDependencies": { "@babel/core": "^7.29.0", "@rolldown/plugin-babel": "^0.2.1", "@types/babel__core": "^7.20.5", "@types/node": "^25.5.0", "@types/react": "^19.2.14", "@types/react-dom": "^19.2.3", "@vitejs/plugin-react": "^6.0.1", "babel-plugin-react-compiler": "^1.0.0", "typescript": "^5.9.3", "vite": "npm:@voidzero-dev/vite-plus-core@latest", "vite-plus": "latest" }, "packageManager": "pnpm@10.32.1", "pnpm": { "overrides": { "vite": "npm:@voidzero-dev/vite-plus-core@latest" } } }Before I started using
vite-plus, I upgraded packages withpnpm up -i -L. It would automatically update the version numbers inpackage.jsonto the latest versions and syncpnpm-lock.yaml.Now that I'm using the
npm:@voidzero-dev/vite-plus-core@latestalias for Vite, how should I upgrade the Vite version?Do I need to keep the version pinned as
latestforever?When I ran
pnpm up -L, it changed tonpm:@voidzero-dev/vite-plus-core@^0.1.12, but the version in theoverridessection did not update. Do I have to manually sync it every time?Additionally, how can I resolve these peer dependency warnings?
These packages all expect Vite 7.0 or 8.0, but the
vite-plus-coreversion I'm currently using is 0.1.12.Beta Was this translation helpful? Give feedback.
All reactions