Ruy Adorno

@ruyadorno.com

Node.js TSC • Founder Engineer at @vlt.sh • Previously Google, GitHub, npm Inc. Opinions are my own. 📍 Montreal 🇨🇦

Excited to share vlt 1.0 along with our hosted registries & ecosystem mirrors now GA! A drop-in npm replacement, built so nothing runs on your machine just because you typed install. → faster delivery → malware blocking at the registry layer → graph-native querying

🥁 𝐒𝐩𝐞𝐚𝐤𝐞𝐫 𝐀𝐧𝐧𝐨𝐮𝐧𝐜𝐞𝐦𝐞𝐧𝐭🎙️ Thrilled to have Filip Skokan on the NodeConf EU 2026 stage! He'll tell us the story of "𝐏𝐨𝐬𝐭-𝐐𝐮𝐚𝐧𝐭𝐮𝐦 𝐂𝐫𝐲𝐩𝐭𝐨𝐠𝐫𝐚𝐩𝐡𝐲 𝐢𝐧 𝐍𝐨𝐝𝐞.𝐣𝐬". 🎟️Don't miss it out, secure your tickets www.nodeconf.eu

Bild

Don't forget! Tickets are on sale now for @nodeconf.eu The conference is being held in beautiful Bologna, Italy on September 29th and 30th We've got a fantastic agenda, wonderful sponsors, and Italian food. The food alone is worth the trip.

Your AI assistant just suggested an npm package. It looks real, it's well-named, it solves your exact problem. It also never existed until an attacker registered the name & filled it with malware. That's slopsquatting. 🧵

Did you know Node.js is redesigning its API documentation? The new beta brings faster navigation, improved search, richer type information, better mobile support, version switching, and so much more. Learn more & preview today at nodejs.org/en/blog/anno...

Node.js — Check out the New Node.js API Documentation Preview

Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.

nodejs.org

A familiar story: the build crashes, so you rm -rf node_modules && rm package-lock.json, then reinstall to get your dev env back. But once the lockfile's gone, your ^ ranges take over. npm install can grab the newest in-range version of everything: poison included when there's a supply chain attack

Ship JavaScript? Hang onto your lockfile | vlt /vōlt/

Pinning dependencies in package.json won't save you in a supply-chain attack — a committed lockfile does. Here's why, and how to install so it holds.

vlt.io

my sister is an incredible artist and therapist. she made me a ceramic mask that hangs in my living room that is one of my prized possessions. she was accepted into an artist residency in italy and has a kickstarter to raise money for her to go. one of the tiers is your very own one-of-a kind masks!

Julia's Italian Art Residency

Please support my participation in the two-week interdisciplinary artist residency Baroque Blue Art & Nature Residency in Italy!

kickstarter.com

🎟️ NodeConf EU 2026 — tickets are live! September 29-30 · Bologna, Italy Hotel Savoia Regency Two days of talks, conversations, and the hallway track that makes this conference worth the trip.

I noticed npm is finally pushing out some of the breaking changes that I wanted to push 5 years ago, so I decided to write something about it, mostly to report and raise awareness that these changes are coming 😊 www.vlt.io/blog/npm-12-...

Beyond disabling postinstalls: how npm install will change in npm 12 | vlt /vōlt/

As part of its planned 12th release, the npm CLI drops automatically running lifecycle scripts on installs as part of multiple planned breaking changes

vlt.io

Landed a few improvements to the error reporting for require(esm) with top-level await (behind --experimental-print-required-tla for now): - No longer 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

Before: extra noisy arrow pointing to internals, no require stack, needs to run the code to find the top-level await location
After: no more noisy arrows, added require stacks to the output, finds location without running the codeNew ERR_REQUIRE_ASYNC_MODULE includes error.requireStack and error.topLevelAwaitLocations metadata properties

If you regularly publish to the npm registry, you might be concerned about package size 😁 But have you heard of PACKUMENT size? News flash: how often you publish, how long your manifest is, how many *exports* you have, can also eventually prevent you from publishing!

Why Drizzle ORM couldn't publish new releases on NPM for a month | vlt /vōlt/

Drizzle ORM recently hit a 100 MB limit in the npm registry and couldn't ship new releases for weeks. What is this limit?

vlt.io