docs: update package information in roadmap section #32881
Conversation
|
|
WalkthroughThe documentation for the Nuxt roadmap was updated to reflect the current status of Nuxt versions. Nuxt v4 is now marked as stable and is available under the latest npm tag, while Nuxt 3 has moved to maintenance mode with support until 31 January 2026. The release date for Nuxt 4 was updated to 16 July 2025, and a projected release for Nuxt 5 is listed for Q4 2025. The end-of-life schedule for Nuxt 4 is set to six months after the v5 release. The release table was revised and reformatted to clarify these changes. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
docs/5.community/6.roadmap.md (3)
62-62: Insert a comma after “v4” for correct clause separation
Add a comma before the non-restrictive clause “which is available asnuxt…”.-The current active version of [Nuxt](https://nuxt.com) is **v4** which is available as `nuxt` on npm with the `latest` tag. +The current active version of [Nuxt](https://nuxt.com) is **v4**, which is available as `nuxt` on npm with the `latest` tag.
66-66: Missing comma after “releases”
For readability, insert a comma after “releases”.-Each active version has its own nightly releases which are generated automatically. +Each active version has its own nightly releases, which are generated automatically.
68-69: Consider naming the otherwise-blank second column header
The second column is currently empty, yet contains version badges in the rows below. Giving it a descriptive header such as “npm badge” or “Version badge” would improve table clarity and accessibility for screen-reader users.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/5.community/6.roadmap.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: ensure that ai-generated summaries accurately reflect the key changes in the pr, focusing on notable...
Learnt from: Tofandel
PR: nuxt/nuxt#0
File: :0-0
Timestamp: 2024-11-11T12:34:22.648Z
Learning: Ensure that AI-generated summaries accurately reflect the key changes in the PR, focusing on notable changes such as the removal of unused imports and variables starting with underscores.
Applied to files:
docs/5.community/6.roadmap.md
📚 Learning: in nuxt, using `rolldownversion` (not `rollupversion`) is intentional when detecting if rolldown-vit...
Learnt from: TheAlexLichter
PR: nuxt/nuxt#31812
File: packages/nuxt/src/components/plugins/islands-transform.ts:202-202
Timestamp: 2025-04-18T18:33:41.753Z
Learning: In Nuxt, using `rolldownVersion` (not `rollupVersion`) is intentional when detecting if rolldown-vite is being used, even though TypeScript may show an error because the property isn't in standard type definitions yet.
Applied to files:
docs/5.community/6.roadmap.md
🪛 LanguageTool
docs/5.community/6.roadmap.md
[uncategorized] ~66-~66: Possible missing comma found.
Context: ...Each active version has its own nightly releases which are generated automatically. For ...
(AI_HYDRA_LEO_MISSING_COMMA)
erwanjugand
changed the title
erwanjugand
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/5.community/6.roadmap.md (1)
62-62: Insert a comma after “v4” for claritySmall readability nit ‒ add a comma after the version number to separate the non-restrictive clause.
-The current active version of [Nuxt](https://nuxt.com) is **v4** which is available as `nuxt` on npm with the `latest` tag. +The current active version of [Nuxt](https://nuxt.com) is **v4**, which is available as `nuxt` on npm with the `latest` tag.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/5.community/6.roadmap.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: ensure that ai-generated summaries accurately reflect the key changes in the pr, focusing on notable...
Learnt from: Tofandel
PR: nuxt/nuxt#0
File: :0-0
Timestamp: 2024-11-11T12:34:22.648Z
Learning: Ensure that AI-generated summaries accurately reflect the key changes in the PR, focusing on notable changes such as the removal of unused imports and variables starting with underscores.
Applied to files:
docs/5.community/6.roadmap.md
📚 Learning: in nuxt, using `rolldownversion` (not `rollupversion`) is intentional when detecting if rolldown-vit...
Learnt from: TheAlexLichter
PR: nuxt/nuxt#31812
File: packages/nuxt/src/components/plugins/islands-transform.ts:202-202
Timestamp: 2025-04-18T18:33:41.753Z
Learning: In Nuxt, using `rolldownVersion` (not `rollupVersion`) is intentional when detecting if rolldown-vite is being used, even though TypeScript may show an error because the property isn't in standard type definitions yet.
Applied to files:
docs/5.community/6.roadmap.md
🪛 LanguageTool
docs/5.community/6.roadmap.md
[uncategorized] ~66-~66: Possible missing comma found.
Context: ...Each active version has its own nightly releases which are generated automatically. For ...
(AI_HYDRA_LEO_MISSING_COMMA)
🔇 Additional comments (2)
docs/5.community/6.roadmap.md (2)
64-64: Cross-check “maintenance updates” wording against the Support Status tableLine 64 states that Nuxt 3 will keep receiving bug-fix and feature back-port updates, whereas the “Maintenance” status in the table (Lines 81-82) is defined as security-patches only.
If Nuxt 3 will indeed receive more than security fixes, consider adjusting the status description or adding a clarifying note to avoid confusion.
68-72: Verify new table links and forthcoming docs path
- The docs column for 4.x points to
/docs/4.x. Ensure that this route is (or will be) live before the site is deployed; otherwise visitors will hit a 404.- Badge links rely on npm version tags—double-check that the
nuxtpackage already exposes the expected v4 versions vialatestbefore the page goes public.No code change required if the links are confirmed, but worth validating.
2 participants
🔗 Linked issue
📚 Description
This pull request updates the Nuxt roadmap documentation to reflect the release of Nuxt 4 as the current active version and clarifies the maintenance and end-of-life timelines for Nuxt 3 and other versions.
Updates to version status and support timelines:
nuxton npm, replacing Nuxt 3.Sources: https://nuxt.com/blog/v4