Add beforeWorkspaceDependency addition/replacement/removal hooks
#6994
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.
What's the problem this PR addresses?
Currently,
@yarnpkg/plugin-essentialsonly provides "after" hooks (afterWorkspaceDependencyAddition,afterWorkspaceDependencyReplacement,afterWorkspaceDependencyRemoval) that fire after dependencies are added, updated, or removed via CLI commands.There is currently no way to intercept or control the behavior before package version suggestions or installations take place. Also "after" hooks do not provide enough information to determine whether the user explicitly specified a version range in CLI commands.
How did you fix it?
Added three new hooks to the Hooks interface in
@yarnpkg/plugin-essentialsthat mirror the existing "after" hooks:Checklist