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

Make react-datetime compatible with React 17.0.2 #792

Closed
josh-annexus opened this issue May 24, 2021 · 2 comments · Fixed by #764
Closed

Make react-datetime compatible with React 17.0.2 #792

josh-annexus opened this issue May 24, 2021 · 2 comments · Fixed by #764

Comments

@josh-annexus
Copy link

I'm Submitting a ...

[ ] Bug report
[ ] Feature request
[x] Support request

Steps to Reproduce

I'm using npm version 7 and getting the following peerDependency error:
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [myProject]
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR! react@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.5.0" from react-datetime@3.0.4
npm ERR! node_modules/react-datetime
npm ERR! react-datetime@"^3.0.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Expected Results

Actual Results

Minimal Reproduction of the Problem

Other Information (e.g. stacktraces, related issues, suggestions how to fix)

@alejandroiglesias
Copy link

alejandroiglesias commented Sep 1, 2021

@arqex could you please merge #764 to fix this?

@alejandroiglesias
Copy link

alejandroiglesias commented Sep 2, 2021

@layneanderson great! Will a new release come out soon? Without publishing this change into npm, it still cannot be installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants