Repository navigation
fix(nuxt,nitro): Accept Nitro 3 betas without narrowing peer support - #25815
Merged
Merged
Conversation
Co-Authored-By: GPT-6 <codex@openai.com>
Contributor
size-limit report 📦Compared: b7e0ea9 (PR test merge using develop at 3c3d423) Against: 3c3d423 (develop) · base run #63935 ✅ Baseline matches: this diff contains only this PR's changes.
|
Contributor
Optional E2E testsAll optional checks were successful. 8 successful. See the run. Successful checks
|
Co-Authored-By: GPT-6 <codex@openai.com>
msonnb
changed the title
msonnb
marked this pull request as ready for review
October 28, 2026 13:17
msonnb
requested review from
chargome,
nicohrubec and
s1gr1d
and removed request for
a team
October 28, 2026 13:17
nicohrubec
approved these changes
Oct 28, 2026
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1663383. Configure here.
| "peerDependencies": { | ||
| "nuxt": ">=3.7.0 || 4.x || 5.x", | ||
| "nitro": "2.x || 3.x" | ||
| "nitro": "2.x || 3.x || 3.0.260311-beta || 3.0.260415-beta || 3.0.260429-beta || 3.0.260522-beta || 3.0.260603-beta || 3.0.260610-beta || 3.0.260903-beta" |
There was a problem hiding this comment.
Fix PR missing regression tests
Low Severity
This fix PR only widens the nitro peer ranges and adds no unit, integration, or E2E test that fails without the new dated betas and passes with them. Existing Nuxt 4 e2e apps use pnpm and would not reproduce the npm peer resolution this change targets. I flagged this because the review rules' Testing Conventions require a regression test on fix PRs.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 1663383. Configure here.
51 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Accept the published Nitro 3 betas so npm can resolve Nuxt 4.6 upgrades without selecting deprecated
nitro@3.0.0and conflicting with Vite 8.Closes #25761