Node.js 26.0.0 (Now with Temporal)

(nodejs.org)

65 points | by aarestad 2 hours ago

8 comments

  • jauco 18 minutes 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)

  • pjmlp 1 hour 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.

  • chrisweekly 23 minutes 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 10 minutes 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 12 minutes ago
      Looks interesting, what's their revenue model? Or how do we know it won't be abandoned in the near future?
  • emilfihlman 2 minutes 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.

  • noodlesUK 1 hour 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 1 hour 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 1 hour 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...
    • culi 1 hour ago
      Until then, a solid backfill has been available for quite some time
  • torgoguys 56 minutes 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.
  • actionfromafar 11 minutes ago
    And here I thought that it was about https://github.com/temporalio/sdk-typescript
  • cute_boi 1 hour 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.
    • postepowanieadm 33 minutes ago
      They should the unexpected and vibe code node to zig. Or Odin for the kicks.
    • HatchedLake721 1 hour 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
      • bel8 57 minutes 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 36 minutes ago
          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.
    • karel-3d 59 minutes ago
      they should rewrite their whole stack by AI from one language to another language, it seems fun.