Skip to content

feat(deps): upgrade upstream dependencies #842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Brooooooklyn wants to merge 1 commit into from
Closed

feat(deps): upgrade upstream dependencies #842

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion packages/core/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@
"@babel/types": "^7.28.5",
"@oxc-node/cli": "catalog:",
"@oxc-node/core": "catalog:",
"@vitejs/devtools": "^0.0.0-alpha.34",
"@vitejs/devtools": "^0.1.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update devtools peer range after version bump

Bumping @vitejs/devtools to ^0.1.0 here leaves packages/core/package.json’s peerDependencies entry pinned to ^0.0.0-alpha.31, which does not include 0.1.x; consumers that install this package alongside @vitejs/devtools@0.1.x will see an unsatisfied peer (and installs can fail under strict peer-dependency settings). The peer range should be widened to include the newly adopted major/minor line.

Useful? React with 👍 / 👎.

Copy link

@cursor cursor bot Mar 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Peer dependency range not updated with devDependency upgrade

Medium Severity

The devDependencies entry for @vitejs/devtools was upgraded to ^0.1.0, but the peerDependencies entry on line 131 still declares ^0.0.0-alpha.31. In semver, ^0.0.0-alpha.31 resolves to >=0.0.0-alpha.31 <0.0.1, so 0.1.0 falls outside this range. This means the installed dev version doesn't satisfy the package's own peer dependency contract, and downstream consumers installing @vitejs/devtools@0.1.0 will receive peer dependency warnings or errors.

Additional Locations (1)
Fix in Cursor Fix in Web

"es-module-lexer": "^1.7.0",
"hookable": "^6.0.1",
"magic-string": "^0.30.21",
Expand Down
209 changes: 161 additions & 48 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading