Jacob Hummer

If anyone stumbles across this issue like I did, here's a trick to nudge your readers into using the GitHub builting TOC button: ```md ↖️ Click for TOC ``` Live...

@Jogai you're absolutely right! Good catch 👍 Alternative image that I think works: ↖️ Click for TOC light mode:  dark mode: 

how would i go about adding a test? 😵 the 'message' and 'pseudo-tty' folders dont seem to support `node --help | head -n1` piping... do they? am i missing something...

ci failures extracted for reading convenience: https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu2204_sharedlibs_shared_x64/41902/console ```sh 09:58:52 not ok 4088 sequential/test-watch-mode-inspect # TODO : Fix flaky test 09:58:52 --- 09:58:52 duration_ms: 120028.02600 09:58:52 severity: fail 09:58:52 exitcode: -15...

i think i fixed ci failures. now uses console.log(). `require()`-ed after the bootstrap() function. do i still need a test? how would i even go about adding such a test?...

i added a test that i think works. it CORRECTLY FAILS on my installed node v21.7.1.

I've used the rebuild-with-feature-flags strategy myself. 👍 It works particularly well when you really want to keep everything in a single file such as when using [the new cargo script...

You can use something like https://www.jsdelivr.com/esm or https://esm.sh/ to import packages in your browser's DevTools on any page you want! (as long as there's no [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)) _i like to use...

i think it works! 

time to figure out how to add tests 😵 i also need to actually run the linter. and make sure i did prrimordials stuff right. and make sure it fits...