fix(nuxt): avoid external nitropack runtime barrel#18
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
onmax
force-pushed
the
codex/fix-nuxt-runtime-config-import
branch
from
June 3, 2026 07:44
3269e11 to
6568e4f
Compare
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.
Narrows the Nuxt runtime config import used by the Nitro validation plugin from the broad
nitropack/runtimebarrel to the config-only runtime entry. This keeps Nuxt node-server output from retaining a live package-runtime import that can pull Nitro virtual imports outside the generated Nitro build context.Adds regression coverage that builds the Nuxt runtime-validation fixture and asserts the generated server output does not contain
nitropack/runtimeor#nitro-internal-virtualimports. Standalone Nitro keeps usingnitro/runtime-config.