feat: Set legacy-peer-deps npm config #64
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
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.
Set
legacy-peer-depsto true, unless explicitlyfalseor"false".Some customer node dependencies may declare the test framework as a peer dependency (e.g. @testing-library/testcafe). As of npm@7, peer dependencies are installed automatically. And even though we account for this by how we handle
package.jsonandpackage-lock.json, settinglegacy-peer-depsexplicitly to true provides a bit of self-documentation on the expected behaviour for peer deps and provides some redundancy.Opted to make this configurable in case we want to modify this behaviour in the future without needing to do a runner release.
DEVX-2573