Add package manager to DiagnosticView #840
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
p-malecki
deleted the
@p-malecki/add-package-manager-info-to-diagnostics
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a package manager status info to the DiagnosticView, this update will help identify issues from using the wrong package manager, especially when multiple lock files are present in a workspace.
It also introduces a new
detailsfield to the DependencyStatus type. This field stores the name of the detected package manager and can also hold version numbers or other relevant details for future needs.How Has This Been Tested:
yarn.lock,package-lock.json,pnpm-lock.yaml,bun.lockb).Screenshots: