fix(nuxt): do not read user's package.json when looking for nuxt deps #27864
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
📚 Description
This is a follow-up on #27507. Noticed we were getting weird issues with
@nuxt/schema
kit versions - and this was because when@nuxt/schema
was not installed explicitly in a pnpm project, Nuxt was silently readingpackage.json
from user's project because the module was resolved as/user/path/@nuxt/schema
and the closestpackage.json
to this nonexistent path was in fact the user project.cc: @huang-julien