Node.js v26.0.0 is out 💚
Temporal API enabled by default, V8 14.6, Undici 8, and key deprecations as we keep modernizing the platform.
Check it out https://t.co/ASREIY1jM0
TypeScript 7.0 Beta is here!
Built on a new native and parallelized foundation, it's already being used on multi-million line codebases.
Read up more here and try it on your projects today!
https://t.co/mYN3MPp1ab
My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
Temporal is now Stage 4 at TC39 🎂🎂🎂
Thanks to all the other champions of JavaScript's new date-time API. It has been a wild ride over many years!
I wrote a blog post explaining how we got here 📜
🧵
@samselikoff When you say "CDN" you're really referring to Vercel, right?
Looking forward to a guide that explains what's required in order to serve cached pages from a different region while streaming the dynamic parts from the origin within a single request-response cycle.
LWJGL 3.4.0 released! Highlights:
* SDL 3 bindings
* FFM-based backend, without JNI or sun.misc.Unsafe
* Runtime bindings generation with the ClassFile API
Full release notes: https://t.co/GKlAxGXzQY
Download: https://t.co/sbkMsAHjgd
⚔️introducing TypeSlayer⚔️ A #typescript type performance benchmarking and analysis tool. A summation of everything learned from the benchmarking required to make the Doom project happen.
It's got MCP support, Perfetto, Speedscope, Treemap, duplicate package detection, and more.
We've got some updates on TypeScript 7! The new native port
- can type-check any project
- supports --build and --incremental
- has rich editor features implemented
- is still 10x faster
and is ready for you to try today!
https://t.co/wPOXTwZVlG
@michaldudak@colmtuite I'm sorry, we were conditionally switching between Popover & Dialog and thought the problem was in both. I've confirmed that Dialog does not have the issue.
@colmtuite Another regression: https://t.co/rudAYE2xQQ
I think it affects all render props on triggers. We're seeing the same error in both Popover and Dialog.
@colmtuite Awesome release! 🪲 We are getting "createContext only works in Client Components" errors in anything that uses floating-ui-react internally (Tooltip, Menu, etc). If we wrap with "use client" it seems to work. This wasn't needed in the previous beta. Is it intentional?