Node.js 26.0.0 (Now with Temporal) (nodejs.org)

115 points by aarestad 5 hours ago

jdthedisciple 2 hours ago

> Upsert (https://github.com/tc39/proposal-upsert): [Weak]Map.prototype.getOrInsert(), [Weak]Map.prototype.getOrInsertComputed()

Their usage of upsert appears different than I was used to:

Me: Upsert = Update or Insert

Them: Upsert = Get or Insert

OptionOfT 20 minutes ago

Reminds me of the weird C++ map operator[] behavior.

If you use that operator and the value doesn't exist, it'll default create one and return a reference to that.

And as I'm writing this I realize why... references cannot be `null`.

bakkoting an hour ago

The proposal used to do more thing and we didn't change the URL after we ultimately arrived at this set of APIs.

pjmlp 4 hours ago

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.

aarestad 3 hours ago

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!

petercooper 3 hours ago

https://nodejs.org/en/blog/release/v26.1.0 is particularly cool as it added initial FFI support.

noodlesUK 4 hours ago

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.

jpsimons 4 hours ago

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.

keeganpoppen 4 hours ago

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...

kaoD 37 minutes ago

That's how you get date bugs.

culi 4 hours ago

Until then, a solid backfill has been available for quite some time

OptionOfT 16 minutes ago

Node v26 doesn't ship with corepack anymore. Annoying, it was a decent way to get pnpm in-band.

chrisweekly 3 hours ago

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.)

KronisLV 3 hours ago

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.

rumblefrog 3 hours ago

Looks interesting, what's their revenue model? Or how do we know it won't be abandoned in the near future?

shimman an hour ago

The same as any other dev tool startup, once money gets tight they will monetize and users will rightfully revolt.

Evan You won't break the cycle, tale as old as time.

lioeters 25 minutes ago

manniL an hour ago

jauco 3 hours ago

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)

pier25 2 hours ago

Initially it didn't make sense to me... but it looks like type striping is really the way to go for future TS.

There's the "types as comments" proposal[1] which could even land on browsers one day.

I started using the erasableSyntaxOnly setting in my tsconfig to get ready for this.

[1] https://tc39.es/proposal-type-annotations/

torgoguys 3 hours ago

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.

sedatk 2 hours ago

Off-topic but, Safari seems to be the only browser that doesn't support Temporal yet. It looks like the only blocker for adopting it on web.

https://caniuse.com/?search=Temporal

owebmaster an hour ago

No but Google wants to control the Web (they do).

jollymonATX an hour ago

(Now with Malware) I joke! It already had malware.

emilfihlman 2 hours ago

It's so sad that node refuses to add websocket server support.

Adding websocket would simplify stuff tremendously, as well as make deployments much, much more secure.

skybrian 2 hours ago

Why more secure?

I see that Deno has WebSockets, but I've never used them: https://docs.deno.com/api/web/~/WebSocket

owebmaster an hour ago

"ws" is regularly the only package in my package.json

actionfromafar 3 hours ago

And here I thought that it was about https://github.com/temporalio/sdk-typescript

cute_boi 4 hours ago

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.

HatchedLake721 4 hours ago

/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

xkcd-sucks an hour ago

Honest question, what isn't compatible? Where I work we've simply replaced node with bun across a lot of overcomplicated + crappy projects, and on my work+personal computers I alias bun/bunx to node/npx with seemingly no issues at all

notnullorvoid 2 hours ago

In my testing Bun wasn't much faster most of the time, usually on par for all non-IO related stuff, and there were some cases with scheduling where Bun was noticable slower.

bel8 3 hours ago

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?

vichle 3 hours ago

postepowanieadm 3 hours ago

They should the unexpected and vibe code node to zig. Or Odin for the kicks.

pjmlp 2 hours ago

I see no reason to leave node in what concerns JavaScript runtimes.

karel-3d 3 hours ago

they should rewrite their whole stack by AI from one language to another language, it seems fun.