Shark · Jun 17

ship it

Matteo Gabriele · Jun 17

Ship it!

Andrew Hudson · Jun 18

amazing! This week I created a web component <time-in> to do this. www.npmjs.com/package/@big...

Thomas Boom · Jun 17

Woah, great!

Bogdan Chadkin · Jun 18

This would be super useful. Every project I built has something similar in user land.

Sean Newell · Jun 17

Do browsers have a built in IANA tzdb that gets updated regularly? I feel like they must do now, but was that only the case since Temporal? So many kB of js libs could be gone! And now even vanilla js too lol.

Jon Kuperman · Jun 17

ship

Philihp Busby · Jun 17

Wouldn't it be easier to just use UTC for everything?

Mårten Thavenius · Jun 17

That was about time.

Donnie D'Amato · Jun 17

I literally built this in my blog years ago. I'd love for it to be native.

Roman · Jun 17

👀

zeu · Jun 17

YES PLEASE i do not want to make another toLocaleDateTimeString utility function ever again

John Bakhmat · Jun 17

I just know that Safari would implement it weirdly that would require custom overwrites. Just like <input type=“search” /> has weird styling

Schalk Neethling · Jun 17

Banda Bassotti · Jun 17

TIL this doesn't exist already.

@ndesmic.bsky.social · Jun 17

Yay. Been wanting this for years: dev.to/ndesmic/how-...

Zacky Ma · Jun 17

@lcas.dev @wil.to Native support for my custom element! 🙃 https://github.com/marchbox/intl-elements/tree/main/src/elements/datetimeformat

JP · Jun 17

Cool, I've mostly given up for standards to get this right! Countless times I've done libraries to write dates or spans like this: 17.6. ke 17.6. keskiviikko 17.6.2026 17.6.–30.6. 17.6. klo 13 17.6. klo 13–15 Not holding my breath for standards to get this right though!

makeworld · Jun 17

@wilkinson.graphics they heard us asking for this yesterday