fix: allow overriding specific build output files with aliases#328
Closed
fix: allow overriding specific build output files with aliases#328
Conversation
7 tasks
Member
|
We have dynamic virtual imports (https://nitro.unjs.io/config/#virtual) that can be used in order to override any import. (I made this feature initially for linked issue in fact)
|
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
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
nuxt/nuxt#13986
❓ Type of change
📚 Description
In some cases, such as the linked issue (which we could resolve by adding an alias to a stub file in the case of
ssr: false), it is helpful to be able to override individual#build/some-file.jsaliases, and to do this we need#buildto be defined last in the object.📝 Checklist