You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In JavaScript engines that implement unicode ICU 72, Date's toLocaleString function returns a "NARROW NO-BREAK SPACE" (U+202F) unicode character before 'AM/PM'.
Maybe also in other cases, but that's the one where I noticed it.
This leads to an error when used in date-fns parse function.
In JavaScript engines that implement unicode ICU 72,
Date
'stoLocaleString
function returns a "NARROW NO-BREAK SPACE" (U+202F) unicode character before 'AM/PM'.Maybe also in other cases, but that's the one where I noticed it.
This leads to an error when used in date-fns
parse
function.To reproduce:
init()
in the console and wait for confirmationYou will get Invalid Date.
But if you remove the space or enter a regular space, it's fine.
Related:
NodeJS change: nodejs/node#45068
Kind of related issue in the v8 chromium engine: https://bugs.chromium.org/p/v8/issues/detail?id=13490
"Normalization of spaces" issue: https://unicode-org.atlassian.net/browse/CLDR-14032
The text was updated successfully, but these errors were encountered: