RFC: I have a new proposal to add new vm Module primitives and a SourceTextModuleLoader API to bring the `--experimental-vm-modules` out of experiments! github.com/nodejs/node/...

TFW you have a meet up next week and you even have a session to facilitate but your tonsils are acting up and your voice is now broken 😅

Just landed in London and planning to go to the GitHub social club in London this afternoon. Wondering if anyone here is joining too, happy to go say hi there!

30 minutes into sleep and I got woken up by iPhone’s bed time alert and I couldn’t fall asleep again. This must have been the most stupid feature ever…

Spring has arrived in Galicia!

A few days in and I think my brain is gradually getting used to it. It’s amazing how a color scheme (or the familiarity of a particular one) can affect your speed of comprehension of the code but it’s useful to force yourself not to get locked into a specific set of schemes…

Finally landed this PR that has been delayed for all sorts of reasons.. Hopefully this will help get rid of the "VSCode remote SSH getting stuck connecting to my server" problem caused by the WebAssembly memory allocation issue for most people when it flows into LTS! github.com/nodejs/node/...

Just updated vscode and now I am not sure if I should just get used to the new default color scheme or set it back to the old one...

This must've been one of the most challenging things I've worked on in a while. Thanks Bloomberg for sponsoring my work on this, and everyone who helped shipping a fix in time!

Wrote a blog post about how this works: joyeecheung.github.io/blog/2026/03...

new post on my personal blog. i think these three areas often go unexplained, so hopefully this explains why some of these packages exist. these are fine to exist but the majority of developers shouldn't have to pay the cost for them.

Oh no ran into this again: thought my trackpad is broken because it was acting weird, turned out I just forgot to turn off my bluetooth mouse that was in my bag

This probably never gets old! Now it's time to think if there's a better way to make it less of a chore...

I will be speaking at #JSNation about the current lifecycle of ESM in Node.js, and the recent changes! Check out my #JSNation badge: gitnation.com/badges/jsnat.... Register via the badge and watch the stream for FREE! See you on June 11 & 15.

⚠️ Security release pre-alert: We will release new versions of 20, 22, 24, 25 release lines on or shortly after 24th March, 2026 in order to address: * 2 high severity issues * 5 medium severity issues * 2 low severity issues nodejs.org/en/blog/vuln...

This must’ve been the biggest (in size) PR I’ve ever reviewed 😬 thanks for bearing with my insistence in hooking into the module loader & intercepting in fs internals, hopefully this would make a class of monkey patching in the wild obsolete and we will have a much more robust public API for this!

I am very excited to announce our partnership @eurosky.social with @igalia.com! The partnership will accelerate the development of independent, European-operated infrastructure for the open social web, enabling developers, organizations, & communities to build new applications. cc @xanlopez.xyz

ECMAScript EXTRA-SPECIAL excitement 😉 🚨🚨🚨 IT'S ABOUT TIME! 🚨🚨🚨 Congrats to @ptomato.name on advancing Temporal to Stage 4 at @tc39.es today 🎉 Temporal is the replacement for the JavaScript Date API 👍

Node.js is moving to one major release per year starting with Node 27! 🚀 ✅ Simpler: Every release becomes LTS. ✅ Predictable: Version numbers now align with the year. ✅ New: A 6-month Alpha channel for early testing. https://bit.ly/4rnosLg

This will work with "useCodeCache": true in the next semver-minor release github.com/nodejs/node/...

Landed initial support for ESM in Node.js SEA: github.com/nodejs/node/... Similar to CJS entrypoints, it only supports importing builtins, so generally require bundling. @nodeland.dev is working on support for VFS in SEA that will unlock loading other modules within SEA github.com/nodejs/node/...

Failed catastrophically at the “don’t look at GitHub” weekend challenge. But on the bright side…

Started iteration on ESM support in the Node.js embedder API with new overloads that likely will be less prone to ABI breakages as more features are added.. github.com/nodejs/node/... Initial support has released in 25.6.0 nodejs.org/en/blog/rele...

This was fun to hack on - a gdb unwinder for V8 JIT-compiled frames on x64. chromium-review.googlesource.com/c/v8/v8/+/75... Also interesting to learn this trick from the gdb source: caller's rsp before call = callee's rbp + 16, and this seems to be a conventional CFA in debuggers

I think I figured out what's going on. Here is another blog post about tinkering with Node.js Core on ARM64 Windows (and tips about reducing the wait time on Windows) joyeecheung.github.io/blog/2026/01...

New blog post on the journey of the new --build-sea flag and how SEA injection works joyeecheung.github.io/blog/2026/01...

This just landed! Thanks @addaleax.bsky.social and @legendecas.bsky.social for the reviews! It will be out in the next semver-minor release of 25, and likely backportable to older LTS - the new workflow is a compatible improvement to the existing postject-based SEA building workflows from v18.x.

Good read. A submission to the European Commission's call for evidence on Towards European Open Digital Ecosystems (importance of OSS for EU tech sovereignty, security and competitiveness). It ends with: > If you work in OSS, consider adding your voice. The feedback period ends February 3, 2026.

Now is the time to realize I have been compiling with host arch = x64 the whole time because for whatever reason I have been using x64 python the whole time to run the configure script 😅

This release contains a bunch of PRs I recently submitted to mark features I contributed to as stable/release candidate. Here is a thread about them 🧵:

This is a mitigation, not a guarantee. Stack space exhaustion recovery is NOT specified by ECMAScript. V8 does it on a best-effort basis. If the recursion depth can be controlled by attackers, explicitly limit the depth. This is what the React and Next.js teams fixed in vercel.com/kb/bulletin/....

We appreciate your patience and understanding as we work to deliver a secure and reliable release. Updates are now available for the 25.x, 24.x, 22.x, 20.x Node.js release lines to address: - 3 high severity issues - 4 medium severity issues - 1 low severity issue nodejs.org/en/blog/vuln...

The Node.js package configuration guide is now live! 🎉 Whether you're creating your first package or migrating to ESM, this guide walks you through it with examples. https://nodejs.github.io/package-examples

Finished two retrospective blog posts on the journey of require(esm) before 2025 ends: joyeecheung.github.io/blog/2025/12... joyeecheung.github.io/blog/2025/12...

Made some progress in my hobby project 🎄 Moving single executable application building into Node.js core for better UX/DX, currently works on macOS and Linux and open for feedback! (No Windows yet because I don't take another laptop with me on vacation 😅) github.com/nodejs/node/...

Good news: I am leaving cold and rainy weather for vacation Bad news: it looks like the location I picked is still cold and rainy (just slightly less so)

When the reproducibility of a serialized object breaks and 1. It doesn’t show up in debug builds 2. There is no obvious pattern in how the bits change Then that might be an uninitialised padding (Spent a couple of hours trying to fix this again…after I forgot how I fixed something similar before)

Does LLVM produce slower RISC-V code than GCC? Currently, yes. Can we make LLVM produce faster code? Also, yes! lukelau.me/2025/12/10/c... #llvm #riscv

Working in an enterprise setup with corporate proxies or custom CAs? Node.js has native support for that. No external dependency required, just configure and continue 👍 Details: https://nodejs.org/en/learn/http/enterprise-network-configuration

WIP guide on making Node.js work in an enterprise network environment… github.com/nodejs/nodej... ⚒️

The changed code is a small fraction of an open source contribution. Your commitment to understand the issue, how your proposed solution fits with the project, and be ready to own and push the review process forward is the biggest chunk of the work. Your effort is the contribution, not the code.

Bumping the stability of a bunch of Node.js features that I've been contributing to...(some of them are about the time; some of them are just forgotten to be promoted to stable 😅)

Got my new passport and said goodbye to the old one that was full 😬 Anecdote: I got my first passport to give a talk at NodeJS interactive in Austin, that was my first trip abroad, my first conference, my first conference talk, and my first English talk all at the same time

Touring/climbing steps in Chongqing

Today I gave a talk at JSConf JP covering the implementation story of recent Node.js module loader changes (compile cache, require(esm) and synchronous loader customization hooks). Very lovely conference! Slides: github.com/joyeecheung/...

Preparing my talk for JSConf JP and I finally drew my mental venn diagram about how Node.js development works 🤪

In an unexpected turn of events, this helped me reproduce a bug that can only be reproduced in a Linux arm64 container (not in bare-metal Linux arm64, or any other containers on other platforms 😅)

Uploaded a demo on how to use nodejs/devcontainer! - Testing a mounted dev branch on a different OS - No need to build V8 from scratch on a fresh checkout (usually) - Testing third-party code with the dev branch in a container www.youtube.com/watch?v=3Nwa... PR: github.com/nodejs/node/...

TIL git-restore-mtime, which is very handy when mounting a local clone to a clone in a docker container while still reusing the build cache from the docker image 😇 (otherwise all the files from the local clone would be too fresh and invalidate the build cache in the container)

Built-in HTTP proxies are now on v22 😇 (Going to update the version mentions in a WIP guide on using Node.js in enterprise network environments)