Date-io v2: Uncaught RangeError: Format string contains an unescaped latin alphabet character `n`

[moshest]

The @date-io library release a new version v2 that's break this module.

Please update docs and require install only version 1.X from @date-io in the meantime.

[nolandg]

For others struggling: if you installed @date-io@2.* you might see the error

Uncaught RangeError: Format string contains an unescaped latin alphabet character `n`

For now, downgrade to @date-io@^1.3.13.

[dmtrKovalenko]

Updated the docs. Also pinning this issue to make it easier to resolve the problem for v3 users

[mwskwong]

BTW, @date-io has explicitly stated that in their release Github page

[niceropez]

Updated the docs. Also pinning this issue to make it easier to resolve the problem for v3 users

They do it!
Look here

[rvanmil]

Would it perhaps be possible to have the proper versions of the @date-io libaries listed as dependencies in this project instead of referring to a note in an installation guide? Tbh I think it's a bit odd we have to manually manage the @date-io dependencies because @material-ui/pickers doesn't specify the versions it requires (and so we now have two outdated dependencies in our projects which need to be pinned to the 1.x release for the time being).

[oliviertassinari]

@dmtrKovalenko Since recently, we can leverage the optional peer dependencies, e.g. mui/material-ui#17211, that, I believe would warn if the version is not correct.

[oliviertassinari]

@dmtrKovalenko Alternatively, what do you think of changing the npm tags (to have latest point to v1 and next point to v2), until we complete the upgrade of the picker components?

[dmtrKovalenko]

Agree, but the main idea is that date-io is also used by other packages. We should not depend on date-io version.

Also there is a specific version of @date-ui/core that points picker to use ‘1.3.11’ and do the peer deps validation.