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

Bug: Dependency conflict with date-fns version 3.0.1 #1999

Closed
greengem opened this issue Dec 20, 2023 · 3 comments · Fixed by #2003
Closed

Bug: Dependency conflict with date-fns version 3.0.1 #1999

greengem opened this issue Dec 20, 2023 · 3 comments · Fixed by #2003
Assignees
Labels
bug Bug or Bug fixes

Comments

@greengem
Copy link

Bug description

When attempting to update dependencies in a project using react-day-picker and date-fns, I encountered a dependency conflict with the latest version of date-fns (3.0.1).

To reproduce

  1. Have a project with both react-day-picker and date-fns.
  2. Run npm outdated to see the available updates.
  3. Run npm update.

Expected behavior

I expected all dependencies to update without any conflicts.

Actual behaviour

npm ERR! Found: [email protected]
npm ERR! node_modules/date-fns
npm ERR!   date-fns@"^3.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer date-fns@"^2.28.0" from [email protected]
npm ERR! node_modules/react-day-picker
npm ERR!   react-day-picker@"^8.9.1" from the root project

Environment

Node.js version: 20.5.0
npm version: 10.1.0
react-day-picker: 8.9.1
date-fns: 3.0.1

@greengem greengem added the bug Bug or Bug fixes label Dec 20, 2023
@limonte
Copy link

limonte commented Dec 22, 2023

@gpbl gpbl self-assigned this Dec 22, 2023
@gpbl gpbl linked a pull request Dec 22, 2023 that will close this issue
@gpbl
Copy link
Owner

gpbl commented Dec 23, 2023

We added support for date-fns@3 in version 8.10. Please upgrade react-day-picker before upgrading date-fns. Thanks!

@greengem
Copy link
Author

Thank you @gpbl I upgraded react-day-picker first, then date-fns 3 and it worked perfectly.

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

Successfully merging a pull request may close this issue.

3 participants