| Tech | Version |
|---------------------|---------|
| material-ui-pickers | 1.0.0-rc.9 |
| @material-ui/core | 1.0.0-rc.1 |
| date-fns | 2.0.0-alpha.8 |
| React | 16.3.2 |
| Browser | Chrome, Firefox |
| Platform | macOS 10.13.3 (High Sierra) |
All works (like a guide https://material-ui-pickers.firebaseapp.com/usage)
Most of the functionality has stopped working (calendar, weekday, text values, etc.)
With [email protected] all works.
I am experiencing the same issue
Oh god :)
Anyway as workaround you can use extending of utils and override broken formats. Example here
If you do - feel free to open a PR.
I would suggest to skip [email protected], since it temporary disables all locales except en-US, ru and eo - see changelog.
From our side, we can just mention in docs that we only support alpha.7 for now
I am experiencing the same issue here. I tried the suggested workaround of using extending of utils and overriding broken formats, but that still did not fix the issue.
Here is the screenshot of the issue I am having:

Actually we would not support new version of date-fns till all locales would be supported.
@dmtrKovalenko @cherniavskii , it's true way, but in the future this work must be done. I agree, that for now we need just to fix docs (support [email protected] only)
I have the same problem too
Closed by #418
@thlee1122 @tatarsky-v
I experienced the same issue. I managed to solve the problem by upgrading material-ui, react, react-dom.
You might need to refactor your imports though.
@MEmmanuel sounds like totally unrelated issue to me.
The issue described by @NKozlov cannot be fixed using your recommendations.
Yes, I was referencing @thlee1122 which is different. (#424 in fact). But your answer in it is better ... :)
I'm using date-fns ^2.0.0-alpha.7 but still see the issue if null of empty string provided as value
@igorlesnenko you should use not ^2.0.0-alpha.7 but actually 2.0.0-alpha.7
We've just updated our date-fns to latest (yes, we had ^2.0.0-alpha.7 in our package.json as well).
This is disappointing to have to go in and revert all of the work we did to upgrade because of this dependency.
Does anyone know of a work-around to this issue?
I made a lame fork to just deal with this issue until it gets sorted properly. Works fine for my team, anyone else is welcome to partake. (FWIW, the new format options are nice, esp. the 'bbbb' one to give noon and midnight as suffixes in addition to a.m. and p.m.)
The reason we're stick to 2.0.0-alpha.7 is that it was stable enough and there were no newer releases for like 6 month.
I think we should wait for [email protected] release, since there's too much breaking changes between new alpha releases.
I had the same issue with the last version so i downgraded to 2.0.0-alpha.7 but now i see only chars
You need to use date fns v16 with date-fns-utils and v7 with date-fns-utils-old
You need to use date fns v16 with date-fns-utils and v7 with date-fns-utils-old
@dmtrKovalenko Can be more explicit about this? I'm having the same issue as @milonite but I'm not sure how to fix it
Most helpful comment
I am experiencing the same issue here. I tried the suggested workaround of using extending of utils and overriding broken formats, but that still did not fix the issue.
Here is the screenshot of the issue I am having:
