prevent run from forcing node 20,22 dep requirement of minimatch v10 #42
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.
Resolves a issues where run.js force upgrades minimatch when regenerating a lock file and forcing node >=20 due to minimatch dep change.
Issues
Fixes
Notes
Alternatives
Make run have minimatch as a required peer-dependency. Most modern package managers will throw an error if the user does not opt to install minimatch. Still not ideal if minimatch is directly use by this package, so not making a PR for this.