[pickers] Add support for date-fns v4

[christopherschroer]

Summary

Date-fns v4 has been released

https://blog.date-fns.org/v40-with-time-zone-support/

Pickers only support up to v3

Examples

No response

Motivation

This would allow developers to take advantage of the new time zone features provided by date-fns v4 without worrying about peer-dependency issues

Search keywords: Date-fns

[LukasTy]

Thank you for creating this issue. 👍
We will be sure to include v4 in the peer dependencies. 😉
As for the timezone support, that is a separate and way bigger topic that we have an issue: #10573 👍

[flaviendelangle]

Wow, I wasn't expecting date-fns@4 before a long time 🤯

@LukasTy are you fine keeping the adapter named AdapterDateFnsV3 until the alpha (where the name imprecision will go away), or do you want to re-export it, something like:

export { AdapterDateFnsV3 } from './AdapterDateFnsV3'
export { AdapterDateFnsV3 as AdapterDateFnsV4 } from './AdapterDateFnV3"

The timezone support should be way easier with the new API, but as Lukas said, it won't come automatically with the update, or at least it will require you to do some workaround that we are not aware of yet. For a good built-in support like the other adapter have, we need to spend time integrating it and making sure everything works correctly.

[LukasTy]

Wow, I wasn't expecting date-fns@4 before a long time 🤯

That's exactly my thoughts. 😆 That's why I didn't even think about another name for the adapter when we introduced it. 🙈

are you fine keeping the adapter named AdapterDateFnsV3 until the alpha (where the name imprecision will go away), or do you want to re-export it, something like:

Yes, I would be completely fine with this compromise, unless we see too much confusion with it, then we can consider re-exporting it aliased. 👌

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

We value your feedback @christopherschroer! How was your experience with our support team?
We'd love to hear your thoughts in this brief Support Satisfaction survey. Your insights help us improve!