Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update peerDependencies to include React 18 #5129

Closed
nil4 opened this issue Mar 30, 2022 · 1 comment · Fixed by #5133
Closed

Update peerDependencies to include React 18 #5129

nil4 opened this issue Mar 30, 2022 · 1 comment · Fixed by #5133
Labels
issue/bug-unconfirmed Issues that describe a bug that hasn't been confirmed by a maintainer yet

Comments

@nil4
Copy link
Contributor

nil4 commented Mar 30, 2022

React 18 is now available: https://reactjs.org/blog/2022/03/29/react-v18.html

Trying to use react 18 together with react-select v5.2.2 (latest version) currently leads to a dependency conflict:

> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: app@0.0.0
npm ERR! Found: react@18.0.0
npm ERR! node_modules/react
npm ERR!   dev react@"^18.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from react-select@5.2.2
npm ERR! node_modules/react-select
npm ERR!   dev react-select@"5.2.2" from the root project

This seem to be related to the peerDependencies defined here:

"peerDependencies": {
"react": "^16.8.0 || ^17.0.0",
"react-dom": "^16.8.0 || ^17.0.0"

Would it be possible to publish a new version which allows react 18 too?

@nil4 nil4 added the issue/bug-unconfirmed Issues that describe a bug that hasn't been confirmed by a maintainer yet label Mar 30, 2022
@alemarra89
Copy link

Same problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/bug-unconfirmed Issues that describe a bug that hasn't been confirmed by a maintainer yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants