Material-ui-pickers: 'KeyboardDatePicker' is not exported from '@material-ui/pickers'

[r0hann]

Even when I imported KeyboardDatePicker, this package is showing "'KeyboardDatePicker' is not exported from '@material-ui/pickers'" error. And also when I check index file I could not find 'KeyboardDatePicker'

[839998664]

Facing the same issue as well...Tried using the DatePicker instead but it throws an error..."Cannot read property 'breakpoints' of null"

[dmtrKovalenko]

Sorry, it's my fault. I have published a prerelease alpha version under the latest tag.
Already fixed.

Simply make yarn add @materail-ui/pickers@next and you will get proper version.

[hadasmaimon]

I use the "4.0.0-alpha.7" version and I get the same error:
"'KeyboardDatePicker' is not exported from '@material-ui/pickers'."
@dmtrKovalenko any help?

[dmtrKovalenko]

@hadasmaimon read the docs and breaking changes

[oliviertassinari]

@dmtrKovalenko Does it worth to have a "Upgrade to v4" guide? Like we had in https://next.material-ui-pickers.dev/guides/upgrading-to-v3?

I wonder, the more we push forward, the more it might feel that the next stable release will be a brand rewrite of the componnets. Maybe this tradeoff: have one but focus on the high-level changes, only? Regarding the timing, should we wait to have made more progress?

[dmtrKovalenko]

@oliviertassinari I am working on more breaking changes as we discussed before, the guide – yes we definitely need it. I planned to make all breaking changes and then simply collect all the release notes into one giant.

But it looks like we will have TOO MANY breaking changes. I feel it will take 5 or 6 pages to describe all the changes we done. We need to consider making codemod scripts for update

[oliviertassinari]

@dmtrKovalenko Haha, right. In this case, maybe we should only describe the high-level changes, where they should spend more time on, then encourage people to "rewrite" the usage they have of the component?

For the Autocomplete, we did something a bit similar, replacing demos with a component, the developers had to rewrite. It has been going well.

[dmtrKovalenko]

This sounds reasonable.

[GouthamJM]

yarn add @material-ui/pickers@latest
Typo

[TOcvfan]

I use version 4.0.0-alpha.12 and I also get this error, I have also tried yarn add @material-ui/pickers@latest and next but with same result..

[oliviertassinari]

@TOcvfan This module does no longer exists after v3. You can use the regular component.