fix(nuxt): do not resolve non-absolute component paths #29036
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-modules/leaflet#80
resolves #29028
📚 Description
We now resolve components that don't have file extensions (#28843) but this is also currently fully resolving paths to libraries in
node_modules/
, which is wrong on several fronts - most notably that the path might be different between node + browser.We can skip this if not passed an absolute path as the intention here is just to add a file extension when a partial path is provided.