Joyee Cheung

No particular reason other than it seems a bit more common when I skim over the common shipping patterns

No more juggling CommonJS and faux-ESM. @joyeecheung.bsky.social revealed how Node.js is moving to full ESM and why the future looks brighter for developers. #NordicJS #NordicJS2025

I think yes! @nordicjs.com

I gave a talk today at @nordicjs.com about shipping Node.js packages in 2025...or how to transition from shipping dual/faux-ESM/CommonJS to shipping ESM directly!

Slides at github.com/joyeecheung/...

The same details as the skeet but on a card with Joyee's avatar

Igalia's @joyeecheung.bsky.social will be speaking about "Shipping Node.js packages in 2025,” focused on migrating dual/faux/CJS packages to ESM-only at Nordic.js on Friday, 3rd October at 10:30 CEST

nordicjs.com/2025/speaker...

Come say hi!

Whenever I travel to a place where dinner starts at normal time I always feel that I've gained at least 3 extra hours per day and there are actually things I can do at night again

But that example is pretty extreme, not every CJS exports thousands of names

Ah, that one, there was already an issue and a suggestion to reduce the perf impact if the package provides a wrapper that makes it easier to parse exports: github.com/nodejs/node/...

…or some heuristics can be used to assume .js in node_modules governed by the same package.json have the same format so that they don’t need to be repeatedly parsed

The issue can be alleviated if more packages explicitly specify the type field; or if the toolchains can reuse the parsed result (e.g. for detecting exports) they could reuse it and not just throw it away after syntax detection.

That is pretty much what Node.js does, except that Node.js does reuse the parsed result because it actually needs to parse it and run it anyway. It warns against results it cannot reuse though (ESM in .js under node_modules without “type” field in package.json).

I noticed, but my connection to GitHub at home has always been slow no matter it’s match day or not 😬

Me: why is it taking forever to git clone when I am trying to build a docker container, what's wrong with my docker configuration

(a few moments later)

Oh I forgot I am doing it a home where the connection to GitHub is just outrageously slow 😭 the wrong is in my provider

Yeah it would be odd to say Node.js resent ESM when folks are actively making it less painful to use / ship. At most, there are still wonky edge cases because of technicalities, but bugs always show up when you try to get two very different semantics work together no matter you love them or not.

If there's some enterprise value not represented in a project mostly built by volunteers, the most probable reason is just: no enterprise is investing in the work about this, or not enough. Then it is unlikely to get done by unpaid volunteers in their spare time until investment comes.

Sometimes it's just "people making wishes that won't get done by itself". For example built-in HTTP proxy and system CA support are important for many enterprise users and requested for years, but only added recently because the companies I and another contributor work for are funding the work.

Node.js maintainers come and go; most people active in 2017 are inactive in 2025, and different people have very different views. There isn't a single person or a team who can speak to the value of the project, it's mostly "if you don't like it, submit a PR and convince the people currently around"

An afternoon tea style breakfast.

I tried not to look at GitHub on this special day and I failed already during breakfast....🥲

I blame this breakfast for taking too long to serve and I got bored!

Landed the configurations as "execArgv" and "execArgvExtension" ("none" | "env" | "cli"), expected to go out in v24.7.0!

github.com/nodejs/node/...
github.com/nodejs/node/...

Got two PRs to my fork of Node.js with AI generated nonsense in the past two weeks 🤨 I get that AI spam is common these days but why my fork?

o.O It includes China (with a contestant that I might have seen on TV before)

Haven't tried to generate core dumps on macOS for a local build for quite some time and just found out that the executable now must be signed with com.apple.security.get-task-allow entitlement to be dumped nasa.github.io/trick/howto_...

Or if you are looking into converting other profiles to load in pprof’s visualisations….perhaps www.kvakil.me/posts/2022-0... still works

Executable loading and startup performance on macOS Recently, I fixed a macOS-specific startup performance regression in Node.js after an extensive investigation. Along the way, I learned a lot about tools for macOS and Node.js compilation workflows th

Samply or xctrace? I wrote some example commands in joyeecheung.github.io/blog/2025/01...

"execArgv" field in the SEA config specifies execution flags to be baked into the SEA and applied when it's launched. "execArgvMode" field specifies whether run-time override is allowed. "sealed" for no override, "env" for allowing override from NODE_OPTIONS, and perhaps another value for more powerful override like `--node-flags="--inspect"`.

RFC: We are adding support for execution command line flag in Node.js single-executable applications. What do you think about this configuration?

github.com/nodejs/node/...

test: deflake sequential/test-tls-session-timeout by joyeecheung · Pull Request #59423 · nodejs/node This patch: Splits the validation tests into a separate file and keep the test focus on functional test of the sessionTimeout option. Increase the testing timeout to 5 seconds in case it takes too...

Somehow I seem to manage to fix it github.com/nodejs/node/...

I feel that it might be similar to a flake I fixed recently: a connection that finishes in no time on a dev machine can take more than a second on some machines in the CI, so always assume it can take longer than that

a bunch of fruit is on a wicker plate on a table . ALT: a bunch of fruit is on a wicker plate on a table .

Trying to deflake a test that was written 12 years ago...

We're kicking this Bluesky party up a notch 🎉 and here to give developers what they want (what they really, really want)!

What Chrome features and topics would you like to learn more about?

Node excitement 😉

Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉

This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍

Many folk contributed 🙏

Node.js — Node.js v24.5.0 (Current) Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.

Node.js 24.5.0 is out: built-in proxy support for `node:http(s)`, experimental WASM modules, upgraded OpenSSL version and so much more. Full changelog and download links at nodejs.org/en/blog/rele...