This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
fix(nuxt): narrow nuxt.config
import protection
#6279
Merged
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 nuxt/nuxt#14461
β Type of change
π Description
This narrows down import protection for
nuxt.config
. Vite will pass the id/nuxt.config.ts
even when aliased or relative imports are used. Webpack will pass the full ID so it's possible to devise imports that won't be caught (but the import ofdefineNuxtConfig
fromnuxt
will be caught).π Checklist