feat(schema): default to bundler module resolution#24837
Merged
Conversation
|
|
danielroe
changed the title
bundler module resolution (#22821)bundler module resolution
This was referenced Dec 21, 2023
This was referenced Dec 21, 2023
danielroe
force-pushed
the
fix/module-resolution
branch
from
9d508b0 to
bdf8dcc
Compare
Member
Author
|
/ecosystem-ci run |
Merged
This was referenced Jan 26, 2024
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.
🔗 Linked issue
#22821
22ce98d
❓ Type of change
📚 Description
(This is a remake of #22821.)
This opts us in to TypeScript
bundlerresolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their
package.json.We'll merge for v3.10 as well as helping ecosystem update in the mean time.
📝 Checklist