You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: import nitro helpers from nitropack/runtime - #3889
📖 Documentation (updates to the documentation or readme)
🐞 Bug fix (a non-breaking change that fixes an issue)
👌 Enhancement (improving an existing functionality like performance)
✨ New feature (a non-breaking change that adds functionality)
⚠️ Breaking change (fix or feature that would cause existing functionality to change)
📚 Description
Since Nuxt 4.6.2, apps with compatibilityVersion: 5 fail to build as soon as they use Content:
"useRuntimeConfig" is not exported by "virtual:#imports", imported by "@nuxt/content/dist/runtime/api/query.post.js"
nuxt/nuxt#36548 now really drops the nitro presets from #imports when experimental.nitroAutoImports is off, which is the default with compat v5. This PR imports useRuntimeConfig, useAppConfig and defineNitroPlugin from nitropack/runtime instead, like the database handlers already do. queryCollection stays on #imports since the module registers it with addServerImports.
I checked it on the Nuxt UI playground and docs with Nuxt 4.6.2. Nuxt 5 support will follow in a separate PR.
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.
📝 Walkthrough
Four server-side files now import Nitro runtime helpers from nitropack/runtime instead of #imports. The plugin continues to import queryCollection from #imports, with its TypeScript suppression comment retained. The summaries report no changes to route behavior, API handling, validation, or returned data.
The import updates are mergeable with no identified blocking risk.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly and concisely describes the main change: importing Nitro helpers from nitropack/runtime.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 4…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The pull request description directly explains the Nitro import changes and the compatibility v5 build failure addressed by the changeset.
Full details: Docstring Coverage
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 4 files.
✨ Finishing Touches
📝 Generate docstrings
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
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
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
#3770
❓ Type of change
📚 Description
Since Nuxt 4.6.2, apps with
compatibilityVersion: 5fail to build as soon as they use Content:nuxt/nuxt#36548 now really drops the nitro presets from
#importswhenexperimental.nitroAutoImportsis off, which is the default with compat v5. This PR importsuseRuntimeConfig,useAppConfiganddefineNitroPluginfromnitropack/runtimeinstead, like the database handlers already do.queryCollectionstays on#importssince the module registers it withaddServerImports.I checked it on the Nuxt UI playground and docs with Nuxt 4.6.2. Nuxt 5 support will follow in a separate PR.
📝 Checklist