fix: support Nuxt 5 and Nitro 3 runtimes - #651
Merged
Merged
Conversation
commit: |
📦 Package Size
All tracked output (11)
Runtime dependencies (13)
Baseline: main_@_20d1192___2026-08-03 · gzip is the comparison metric · changes below 16 B gzip are ignored |
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
1 participant
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.
🔗 Linked issue
Resolves #605
❓ Type of change
📚 Description
Nitro 3 no longer exposes the
nitropack/runtimeand H3 entrypoints used by sitemap handlers. Server imports, route rule matching, and generated Nitro types now usenuxtseo-shared5.3.8. Event scoped source requests usefetchWithEvent, and the module aliases its ownofetchdependency so strict pnpm installs can bundle the shared runtime bridge. A packed Nuxt 5 fixture builds and serves the generated sitemap.