feat: require packageManager in package.json #8017
Merged
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.
Description
With 2.0 we will now be requiring a
packageManager
field inpackage.json
as this is a best practice and it helps us behave in a deterministic manner.The actual code change is very straightforward as we remove our package manager inference code and return an error if reading package manager from
package.json
fails.Most of the PR is updating tests.
Testing Instructions
Updated unit tests