This repository was archived by the owner on Apr 6, 2023. It is now read-only.
fix(nuxi): ensure nuxi upgrade runs in rootDir#6707
Conversation
✅ Deploy Preview for nuxt3-docs canceled.
|
pi0
reviewed
Aug 17, 2022
Collaborator
Author
|
The second So in fact my fix to use the package.json lookup as a fallback should be its own PR |
Member
|
It is because of CJS requires cache ( framework/packages/nuxi/src/utils/cjs.ts Line 39 in 6a39155 |
Collaborator
Author
Nice, that worked a treat as far as I can tell |
nuxi upgrade runs in rootDir
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
❓ Type of change
📚 Description
When using
nuxi updatecommand with a custom path, it won't honour that path when running the package manager install, instead, it will always run in thecwd.This is apparent in a monorepo or sub-path nuxt installs.
For example, run in this repo
yarn nuxi upgrade ../some-nuxt-app --forceand you'll see it modifies the frameworks package.json and lock.In providing the proper path, a new issue appears where the
getNuxtVersionfails. It seems like a cache issue where it's resolving to the old version path, leading to a failure to read the file, as it didn't exist.Exception
Logs
As a work-around I've set it up to read from the package.json's dependency, which should be fairly safe.
📝 Checklist