refactor(nuxt,schema,vite,webpack): use unplugin for vfs#29165
Merged
refactor(nuxt,schema,vite,webpack): use unplugin for vfs#29165
Conversation
|
|
4 tasks
Member
Author
|
current test failures:
|
Merged
danielroe
added a commit
that referenced
this pull request
Oct 9, 2024
Kamsou
pushed a commit
to Kamsou/nuxt
that referenced
this pull request
Feb 5, 2025
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
2 participants
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
context: #29142
📚 Description
this migrates away from
webpack-virtual-modulesin favour of using unplugin to provide the nuxt vfs. it means we can use a consistent implementation that is bundler-agnostic.Some key differences:
#build/<filename>paths stripped it - this should not make a difference to resolution but might if manually accessingnuxt.vfs.clientand.serversuffixes in the vfs for conditional resolution in server vs client#buildis now innuxt.options.aliasagain\0virtual:nuxt:is the prefix - in line with vite convention and other plugins🚧 TODO