


She/Her. I contribute to Node.js and V8.



Landed JS argument inspection support in the GDB & LLDB plugins for V8, for both live and coredump debugging - bt now shows previews of JS arguments for JS frames - New `v8 args` command to show arguments of selected frame - `v8 inspect` now takes this, arg names and indices

It's been a great experience to contribute to the V8 upgrades for the 27 release and improve the V8 upgrade process in Node.js in the past months. Thanks @TechAtBloomberg for supporting my work on this :D
Last week, the new Node.js 27 Alpha release upgrades V8 to version 15.6, from the 14.6 used by Node.js 26. Let's take a closer look at what this means for developers and what the new version of V8 brings. - New JS features and language changes - Performance improvements - Memory usage and GC changes - Diagnostic and tooling changes - Behavior differences ..and more! nodejs.org/en/blog/announcem…

Observations: - It was easier to find multipage spec and check history with the C++ spec anchor compared to ecma262 - pre-commit CI coverage of high-impact C++ compiler projects is small when compared to Node.js/V8 - There is a visible test262-shaped void in the C++ world

There were more docs to update when changing semantics in Clang, had to educate myself with the release process before finishing the commit Clang commit github.com/llvm/llvm-project…

There was a bit of a shock for me when navigating in the GCC codebase and the git blame annotation in my editor said the code was as old as myself GCC commit gcc.gnu.org/cgit/gcc/commit/…

Landed fixes in GCC & Clang for [expr.static.cast]/8 wrong-code bugs when investigating a V8 bug related to it. Previously: enum Flag : bool { kNo, kYes }; static_cast<Flag>(2); // kNo in GCC ❌, kYes in Clang ✅ static_cast<Flag>(0.5); // kNo in GCC and Clang ❌

Added some new commands to the GDB & LLDB plugin for V8.. `v8 source`: shows the JS source of the selected frame `v8 isolate`: find the isolate address in the current thread, works from the coredump too (implementing that in LLDB was quite a bit of challenge!)

Is there anyone using the @nodejs --use-largepages=on flag? We are considering dropping it. Let us know!

Made the new debug helper plugins work for Node.js + bleeding edge V8 🌟 Verified it works in LLDB (Linux, macOS) & GDB (Linux), both in live and coredump debugging Going to backport the patches to Node.js when the object inspection is more polished and it stablizes bit more..

PR: github.com/nodejs/node/pull/… & github.com/nodejs/node/pull/… This will be released in the upcoming v26.5.0 github.com/nodejs/node/pull/…

Landed some improvements to errors for require(esm) with top-level await (behind --experimental-print-required-tla for now): - No need to run the code to collect the TLA locations, so it can be enabled by default soon - Added require stack and location metadata to the error

New to open source, or wondering how to get your first Node.js contribution landed and released? Check out our new first-time contributors guide, with practical tips and answers to FAQs about working with our volunteer-driven model. Welcome aboard! 🤝 github.com/nodejs/node/blob/…

Today I gave a talk @thejsnation about the life cycle of ESM in Node.js, how it differs in other environments and the new features that will affect these stages. Slides: github.com/joyeecheung/talks…

Moving along with the debug_helper-based LLDB & GDB V8 plugins, this now supports basic object inspection! It was fun to write tests that deliberately corrupt the memory and ensure the plugin falls back gracefully, something I've never tried before when maintaining other plugins!