-
Notifications
You must be signed in to change notification settings - Fork 6
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
Could not resolve dependency #13
Comments
Hi @ccorral1-tenco, Yes. I'm currently a bit busy with work and other things, but I have a plan to update all my libraries' dependencies as well as make them peer depend on React 18 besides older versions of React. I'll keep you posted! Thank you for using this package. |
Let's keep this issue open for now, I'll track it. |
BTW, are you experiencing any issues when using this |
Right now I don't have any problems with the library. The only inconvenience is that there are |
@tonix-tuft when this ticket going to be resolve. because I'm to getting same error |
I am getting this error when trying to install this package
I fix the issue using --legacy-peer-deps command.
But I was wondering if this package will update some day to the newer versions of React
`
$ npm install react-tempusdominus-bootstrap --legacy-perr-deps
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! react@"^18.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.0.0 || ^16.0.0 || ^17.0.0" from [email protected]
npm ERR! node_modules/react-tempusdominus-bootstrap
npm ERR! react-tempusdominus-bootstrap@"*" 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.
npm ERR!
npm ERR! See C:\Users\user\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Local\npm-cache_logs\2022-08-10T17_49_36_406Z-debug-0.log
`
The text was updated successfully, but these errors were encountered: