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
As @climba03003 mentioned, I don't believe this is an issue, but a feature that comes with updating Node.JS, if you disagree, please elaborate on your concern.
My concern regarding this is that - in a minor version change, there is a backwards compatibility break. If you transition from 20.11->20.12, and rely on this functionality, it's broken, which goes against the semver I believe Node uses
I don't believe these changes are documented anywhere (at least they weren't noticable), and I didn't expect a BC break with a minor version.
It may seem like a backwards compatibility break, but it's just keeping the Unicode standard. All of this locale formatting is standardized by Unicode, so we are just following the changes.
Version
v20.12.1
Platform
Darwin cube.local 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020 arm64 arm Darwin
Subsystem
No response
What steps will reproduce the bug?
Test case:
https://github.com/Mezzle/node-date-format-bug
Same code run in both 20.11.1 and 20.12.1 returns different results.
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
it is expected that the date is consistent across versions.
What do you see instead?
I see that 20.12.1 has a missing
,
difference.Additional information
No response
The text was updated successfully, but these errors were encountered: