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
Hmm thanks - I do seem to have a different ICU version (74.2).
@aza547 You'll probably need to check with Electron which ICU they're using. If they're not using the one bundled in Node.js then they'll need to patch the timezones independently.
Activity
avivkeller commentedon Apr 7, 2025
Node.js gets it's timezone data from ICU, and it not directly responsible for the timezones presented.
LiviaMedeiros commentedon Apr 7, 2025
In the
mainbranch with built-in full-icu, this is already resolved:The PR that fixes this is #57455 which is not included in release yet.
An alternative solution is building Node.js locally with
--with-intl=system-icuflag and providing system-wide ICU with newer version.Closing this as resolved, feel free to reopen if this doesn't look right.
aza547 commentedon Apr 7, 2025
Hmm thanks - I do seem to have a different ICU version (74.2).
I saw that #57685 was in the Node 20.19.0 tag, which describes the time zone change in question, guess the PR you linked is also required.
Anyway - thanks for the response. I'll sit tight till there is a new release I can pick up.
richardlau commentedon Apr 7, 2025
20.19.0 from https://nodejs.org/dist/v20.19.0/node-v20.19.0-win-x64.zip appears to give the expected result for me:
richardlau commentedon Apr 7, 2025
@aza547 You'll probably need to check with Electron which ICU they're using. If they're not using the one bundled in Node.js then they'll need to patch the timezones independently.