🦋.

Again thanks @TechAtBloomberg for supporting my work :). Next stop: write a guide on how to use the newly added builtin support for proxies and custom CA certificates to smooth out adoption of Node.js within a restricted network.

This can be used together with the proxy support in use cases where it needs to be enabled dynamically instead of through --use-system-ca, and reduces needs for monkey-patching TLS which is already done by several npm packages to achieve a similar goal

Landed a Node.js API for configuring the CA certificates used by the built-in HTTPS/TLS clients. To add certs installed in the OS:. tls.setDefaultCACertificates(tls.getCACertificates('default').concat(tls.getCACertificates('system'))).

@TechAtBloomberg For a mini roadmap of proxy support, there's a tracking issue

Thanks @TechAtBloomberg for supporting my work on this! It's also personally interesting to me to work on because the reason why I got interested in how computers work -> programming was proxies :).

Landed support for proxies in Node.js http/https builtins To enable proxies from *_PROXY env vars: use NODE_USE_ENV_PROXY=1. This was already implemented for fetch and released in 24 - soon the old builtins will also support it.

RT @nordicjs: 💫 Say hello to one of our speakers at Nordic.js 2025: @JoyeeCheung!. Joyee is a compilers engineer at @igalia, and one of the….

Posting again here because Shiya has the pictures of the event where I met Mikeal. I think I would not be contributing to Node.js as much as I do now if I had never met him. It's sad to lose someone who has so much impact on so many people. Thank you for everything. RIP.

Slides of my talk at the Web Engine Hackfest - Bridging CommonJS and ESM in Node.js, or implementor's tales of require(esm)

Trying to collect some data: what package that you know/maintain have transitioned to shipping ESM-only/ESM-first after it's unblocked by the support of require(esm)? Any tips/experiences to share?.

RT @nodejs: Trip report of the Node.js Collaboration Summit in Paris is now live✨ . Blog: Recordings: https://t.c….

RT @robpalmer2: Node excitement 😉. Thanks to @JoyeeCheung & @legendecas for this blog post describing what happened at the @nodejs Collab S….

RT @satanacchio: Node.js v20.19.0 is out 🤩. This is a special minor release ✨.Although v20 is in maintenance mode, meaning only patch are e….

This will likely go out in the next semver-minor release of v23 and will probably be backportable. Initial PR is in And as always thanks @TechAtBloomberg for supporting my work ❤️.

The new hooks are also run in the same thread as the modules being loaded & where they are registered, which means they are easier to debug (no more console.log() getting lost) and do not have the many deadlock issues haunting the module.register() hooks.

This complements module.register() hooks - the new hooks fits better internally and cover all corners in the module graph; whereas module.register() previously could not cover require() while it was in-thread, and still cannot cover createRequire() after being moved off-thread.

Landed module.registerHooks() in Node.js ✨.These customization hooks are run for modules loaded by require(), import(), and functions returned by createRequire() in the same thread they are registered, which makes them easier for CJS monkey-patchers to migrate to.

🎉 require(esm) has been unflaged in v22.12.0! We are also planning to unflag it on v20.x later if it goes well in v22.x. As before please try it out and report any bugs you find. (hopefully none, but with how wild the module loading edge cases can be, one never knows!).

RT @43081j: here's a quick update on what the @e18e_dev community has been up to this past month (a lot!💙)