Tangent: if you use Node.js at build time you should check out VitePlus https://viteplus.dev
(No affiliation, just a fan of VoidZero's consistently excellent tools.)
Oh hey, they're the people behind Oxlint and Oxfmt: https://oxc.rs/
I moved some projects over to those from ESLint + Prettier and while the compatibility isn't 100% (I didn't need that), and the time to process a codebase went from like way over a minute with the old tools to a few seconds with theirs.
Looks interesting, what's their revenue model? Or how do we know it won't be abandoned in the near future?
Also the release that drops typescript transforms: https://github.com/nodejs/typescript/issues/51
(I’m not disagreeing to remove it. It just took me a while to find out what happened to it)
26.2.0 is already out, why link to the previous release?
https://nodejs.org/en/blog/release/v26.2.0
What I would expect with the inclusion of temporal, is having a section on nodejs docs about Rust addons, alongside the C and C++ sections.
That's on me - I saw v26 was released, but didn't realize they'd already done a point release in the ensuing 2-3 weeks!
https://nodejs.org/en/blog/release/v26.1.0 is particularly cool as it added initial FFI support.
And here I thought that it was about https://github.com/temporalio/sdk-typescript
I thought this was the release where the built in sqlite got its experimental tag removed, but I don't see it in the release notes. THAT'S got me excited more than Temporal. A stable API, huge utility and one less dependency.
I'm really looking forward to the temporal api being universally available. Moment and Luxon are fairly good but sensible date/time handling is something that really ought to be baked into the platform ootb.
I always thought the old Date is kind of elegant... increment anything with an overflow and it all wraps around correctly, like `d.setDate(d.getDate() + 100)` to advance a date 100 days. "March 208th" is interpreted like you'd expect, as are the hours and minutes and such.
Of course, complete lack of non-local non-GMT time zones is a huge downside.
i'm pretty sure all that stuff works w/ Temporal... Temporal is extremely well-designed, in my experience. the js date object, on the other hand, has insane pitfalls, and i say this as someone who thinks not understanding JS ASI is a "skill issue", among other happily-un-"ergonomic" worldviews...
Until then, a solid backfill has been available for quite some time
Node JS team should look into bun and make progress. They are somewhat stable, but bun have lot of features and is more performant than Node.
They should the unexpected and vibe code node to zig. Or Odin for the kicks.
/s ? Bun is not yet (ever?) compatible with Node. I'm sure if Node JS could trim the fat with breaking changes they'd be fast too
I expect bun to run almost everything that node runs these days. They have an extensive test suit to ensure that.
Even the complicated NextJS runs with Bun: https://nextjs.org/conf/session/nextjs-bun
Do you have a source for your claim?
Maybe if you start from scratch with a new project, but when migrating an old project it's definitely not a drop-in replacement. I try once or twice per year, but it's not worth the effort when the upside isn't that big.
they should rewrite their whole stack by AI from one language to another language, it seems fun.