Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by 698969 on Thursday March 12, 2026 @06:09AM
(#47348578)
That looks neat although your package is missing a link to the source repository.
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by anowell on Thursday March 12, 2026 @07:58AM
(#47349398)
Good catch. Will get that added today.
github.com/howie-code/temporal-fun
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by lightwords on Thursday March 12, 2026 @06:30AM
(#47348743)
Word of warning Temporal relies on the Intl API for formatting, and support in Chrome is very limited due to their binary size constraints. As a result, you'll need to polyfill unsupported languages using format.js
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by rafram on Thursday March 12, 2026 @06:43AM
(#47348872)
$ du -sh '/Applications/Google Chrome.app'
1.3G /Applications/Google Chrome.app
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by lightwords on Thursday March 12, 2026 @06:56AM
(#47348978)
There are numerous reports on this being an issue e.g. https://issues.chromium.org/issues/40624456
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by anowell on Thursday March 12, 2026 @08:05AM
(#47349449)
Thanks for the heads up. Will think on this and will probably just document the polyfill.
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by jacquesm on Thursday March 12, 2026 @09:01AM
(#47349980)
That's complete crazy.
Re:Temporal: The 9-Year Journey to Fix Time in JavaScript
by TimTheTinker on Thursday March 12, 2026 @10:52AM
(#47351439)
Format.js polyfills a lot of stuff that's already supported in modern browsers, and seems to prefer its own polyfills to the native APIs.
Is there any way to force it to only use (and bundle) the polyfills that are needed assuming 2025+ era browsers?
npmjs.com/package/temporal-fun