chore(yarn): update to use js config for constraints #11290
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
Josh-Walker-GM
added
release:chore
Josh-Walker-GM
force-pushed
the
jgmw/chore-yarn-constraints
branch
from
607e250
to
1074bab
Compare
Josh-Walker-GM
force-pushed
the
jgmw/chore-yarn-constraints
branch
from
1074bab
to
fbea266
Compare
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.
We currently use a prolog file to define the constraints yarn applies when you run
yarn constraints(which is run withyarn check).You can see here that yarn states this format should be considered deprecated. Instead a
yarn.config.cjsfile is recommended. This change switches our current prolog one to this new js one.I added rules to enforce some consistent and correctly specified fields are present on our package.json files. We can add to this in the future should we wish to.