You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version mismatch is caused by adherence to semantic versioning in Yarn's Dependency Versioning, in particular the Caret Ranges which means that eslint@^5 || ^6 translates to >=5.0.0 <7.0.0, and packages.json has the eslint package pegged at version ^7.3.0.
To Reproduce
Steps to reproduce the behavior:
Run yarn add eslint-plugin-testing-library
See error
Expected behavior
Per the discussions in testing-library/eslint-plugin-testing-library#139, there should be no difference in behavior after updating eslint-plugin-testing-library to include eslint@^5 || ^6 || ^7 in the peer dependencies except that yarn will stop displaying the warning.
Screenshots
Versions (please complete the following information):
Describe the bug
Until testing-library/eslint-plugin-testing-library#139 is merged and released,
yarn
will continue to complain about a peer dependency version mismatch betweeneslint
andeslint-plugin-testing-library
:The version mismatch is caused by adherence to semantic versioning in Yarn's Dependency Versioning, in particular the Caret Ranges which means that
eslint@^5 || ^6
translates to>=5.0.0 <7.0.0
, andpackages.json
has theeslint
package pegged at version^7.3.0
.To Reproduce
Steps to reproduce the behavior:
yarn add eslint-plugin-testing-library
Expected behavior
Per the discussions in testing-library/eslint-plugin-testing-library#139, there should be no difference in behavior after updating
eslint-plugin-testing-library
to includeeslint@^5 || ^6 || ^7
in the peer dependencies except thatyarn
will stop displaying the warning.Screenshots

Versions (please complete the following information):
development
)Additional context
The inclusion of
eslint-plugin-testing-library
is part of the effort to improve testing infrastructure using React Testing Library.The text was updated successfully, but these errors were encountered: