fix(cli): skip local packages during global update#1961
Closed
liangmiQwQ wants to merge 1 commit into
Closed
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
Collaborator
Author
|
This PR has some blockers (Vite+'s global alias bug, global packages version handling bug), and to follow npm's behavior there are tons of things need to deal with, |
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.
The current global update flow can treat packages installed from a local path or tarball like normal registry packages. That means
vp update -g some-packagemay try to update a package that was originally installed from./pkg.This PR records whether a managed global package was installed from local filesystem content. Global outdated/update checks now skip packages with that metadata, including named updates like
vp update -g some-package, which follows npm's behavior for local global installs.Legacy metadata stays readable and defaults to non-local.
🤖 Generated with Codex