Drop @types/react
peer dependency from ^18.2.25
to ^18.0
#2211
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.
Overview
According to the DefinitelyTyped project FAQ here,
@types
dependencies should align with the MAJOR.MINOR of the source project, while the PATCH version is managed independently.This alignment helps prevent dependency duplication in the
node_modules
folder, particularly for projects using pinned or tilde versions.Below is an example of a project with the
@types/react
dependency version lower than the one required by the currentreact-redux
project peer dependency.This is the output of running
yarn install
:Here is is the output of running
yarn explain peer-requirements <hash>
:This output advises the user to update their dependencies to match those required by
react-redux
in order to avoid duplication.This PR
@types/react
peer dependency from^18.2.25
to^18.0