fix(nuxt): expose nuxt/schema subpath for augmentation
#18922
Merged
Conversation
This file contains 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
|
|
danielroe
changed the title
nuxt/schema subpath for augmentationnuxt/schema subpath for augmentation
antfu
approved these changes
Feb 10, 2023
Merged
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
resolves #18807, resolves #18512, resolves nuxt/content#1884
❓ Type of change
📚 Description
This PR moves Nuxt to use a single target for augmenting Nuxt options to avoid collisions between different versions of schema in a project. (While there can be multiple versions of schema, there should only be ever one installation of
nuxtas this is a devDependency of layers and modules.)📝 Checklist