Joyee Cheung

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...

Encountered a 4 hour delay of the flight and ended up staying in a hotel in Santiago because it’s already past 2am after I got out of the airport. Well, might as well spend a weekend? 🤨

Forgot to remind the border guard to reuse already stamped pages for stamps and now I lost one more blank page on my passport which is already running out of blank pages for visas….😖

Announcing TypeScript 5.9 RC - TypeScript Today we are excited to announce the Release Candidate (RC) of TypeScript 5.9! To get started using the Release Candidate, you can get it through npm with the following command: npm install -D typescr...

TypeScript excitement 😉

TS 5.9 RC is out 🎉

🔶 `import defer` by @nicr.dev
🔶 module: "node20" for require(ESM)
🔷 --init has modern defaults (no downleveling)
🔷 Docs: Inline summaries for DOM APIs
🔷 IDE: Expandable hovers to drill into Quick Infos
🔷 Perf: Faster type instantiation & file existence

I've been enjoying the talks at GUADEC 2025 and tomorrow I'll be on the stage myself, talking about what's new in JavaScript and TypeScript for GNOME development! (Sneak peek: in GNOME 49 we'll get Temporal 😄)

Come see me live or follow along online at 10:10 CEST!

events.gnome.org/event/259/co...

Is next stop growing your own tomatoes or are you already growing them?

For finding nearest package.json there is also now nodejs.org/api/module.h...

a man wearing headphones and a wig says i 'm alive ALT: a man wearing headphones and a wig says i 'm alive

I survived 4 meetings from 5:30 to 18:00 today

doc: add Aditi-1400 to collaborators by Aditi-1400 · Pull Request #59157 · nodejs/node Fixes: #59064

Big welcome to @adt314.bsky.social , the newest @nodejs.org collaborator! 🎉
I had a great time onboarding her, together with @joyeecheung.bsky.social .

github.com/nodejs/node/...

Again thanks @bloomberg.com 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
bsky.app/profile/joye...

crypto: add tls.setDefaultCACertificates() by joyeecheung · Pull Request #58822 · nodejs/node This API allows dynamically configuring CA certificates that will be used by the Node.js TLS clients by default. Once called, the provided certificates will become the default CA certificate list r...

Landed a new Node.js API for configuring the CA certificates used by the built-in HTTPS/TLS clients. github.com/nodejs/node/...

Add certs installed in the OS to the embedded Mozilla bundle:

tls.setDefaultCACertificates(tls.getCACertificates('default').concat(tls.getCACertificates('system')))

AFAIK the need for this is still well alive in different organisations…or countries ;)

Tracking issue: HTTP_PROXY/HTTPS_PROXY/NO_PROXY support in Node.js · Issue #57872 · nodejs/node Support https/http proxies via HTTP_PROXY/HTTPS_PROXY/NO_PROXY in fetch() (behind NODE_USE_ENV_PROXY) Initial support #57165 align with curl: do not tunnel for http proxy nodejs/undici#4083 align w...

For a mini roadmap of proxy support, there's a tracking issue github.com/nodejs/node/...

Thanks @bloomberg.com 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 :)

http,https: add built-in proxy support in http/https.request and Agent by joyeecheung · Pull Request #58980 · nodejs/node This patch implements proxy support for HTTP and HTTPS clients and agents in the http and https built-ins`. When NODE_USE_ENV_PROXY is set to 1, the default global agent would parse the HTTP_PROXY/...

Landed support for proxies in Node.js http/https builtins github.com/nodejs/node/...

To enable proxies configured from *_PROXY env vars: use NODE_USE_ENV_PROXY=1.

This was already implemented for fetch and released in 24 github.com/nodejs/node/... - soon the old builtins will also support it.

Lago Ercina with Picos de Europa in the backdrop

Got disconnected in the mountains for a while today and it was great!

Objects with decorative patterns from various paleolithic cultures in Asturias.

Itinerarios de barro de Astorga, Roman traveller’s roadmaps.

Architecture fragments from churches in the kingdom of Asturias, it’s impressive that the museum made it clear that the whole alliance was a propaganda :)

The museum is in a former convent. The cloister is still in restoration.

I did want to stay away from writing code this weekend, but then it suddenly dawned on me why a test I was debugging was failing after cruising in the museum for a day…so I went back to my laptop and fixed it.

In other news, Museo Arqueológico de Asturias was pretty cool!

I have an impression that single quotes are weird on Windows cmd, or it’s just in a different universe, so depends on whether the argument parsing library you use can actually make it work for you

Congratulations! Well-deserved!

Ecma International Excitement 🎉

Last week, two TC39 members, Rob Palmer (@robpalmer.bsky.social) and Michael Saboff, received the Ecma Recognition Award for their contributions to Ecma, including TC39.

Or how to do memory/perf profiling in production, in general :)

Why don't we use jemalloc? · Issue #21973 · nodejs/node Note: while switching to jemalloc might be unoptimal, it could be still useful to gather information about positive and negative implications of jemalloc usage. Let's do that in this issue. I am no...

Just got pinged by acquaintances about this which affects stability of Node.js in production github.com/nodejs/node/... - and suggested them to PR to nodejs.org/en/learn/dia...

More in zhuanlan.zhihu.com/p/675317993 (Chinese)

Learning how to switch to jemalloc might be useful for advanced workshop

The tags might be rendered correctly if the wrong encoding use shares the initial range with ASCII and then once out of that shared range it started to be bogus. If it’s this short, it could be an error message.

I know Chinese and I think you might want to try changing the encoding of the web page manually in the browser, maybe to UTF-8 or an encoding the relevant country might be using (this used to be a common problem in China back when GBK in IE was common).

Reminded me the time when my bank’s website kept refusing a transfer with an cryptic message “data transmission error” and support kept asking me to check my connection until I realized they simply had issues with ñ in the address after inspecting the network responses with DevTools

Part of me wants a new laptop after coming across a bunch of posts about framework randomly

Part of me says: stop, you have more than enough electronics 😩

Wrote a couple of edge case tests and expected them to fail with my implementation with some useful traces for me to debug and make it work. And to my surprise.....they didn't fail at all. Debug logs showed that it was working as expected. 😮