
Go read his full write-up and tell me: what's the most annoying thing you ever had to configure before your first install? 👇 🪄 vlt.io/blog/vlt-1-8

JavaScript package registries & tooling for teams that move fast.

Go read his full write-up and tell me: what's the most annoying thing you ever had to configure before your first install? 👇 🪄 vlt.io/blog/vlt-1-8

We interviewed the person behind this big change in vlt (no setup and simpler registry resolution) 🎙️ New machine? Install vlt, run vlt install, done. No account, no token, no config 🤯 We asked @RuyAdorno, our staff engineer (yep, he used to work on npm itself), why this is such a big deal: “This is a major milestone for the vlt platform as it’s now ready to serve consumers of open source packages via our public npm registry mirror, which makes it safer and faster to install dependencies in your project.” Before 1.8, a fresh machine needed vlt setup or a registry in your config before the first install. Now it just works out of the box. And if you already have your own registry configured, it still wins, so your setup keeps working like before.

It's MIT licensed and we accept contributions and feedback, so come try it, open an issue or a PR, and of course LEAVE A STAR ⭐️⭐️⭐️ 🪄 github.com/vltpkg/affordance… /6

Try it now: vlt install @affordances/md vlx -y @affordances/md init That's it: every page answers /page.md or Accept: text/markdown, right out of the box 🤯 /5

With it, you can: ✅ serve every page as Markdown, generated from the HTML your app already renders ✅ return a graph of each page's contents and the actions it offers ✅ define an action once and get a server action, an HTTP endpoint, a WebMCP tool and an MCP tool ✅ expose your whole site as an MCP server /4

We believe SEO has changed. A lot of people still wonder how to do it for agents, so we built something to make it simpler and get you value as fast as possible. /3

Check out our newest open source contribution (yeah, it's free!) Meet Affordances: with it, agents can reach your website, browse it, read what it can do, and get the information they need as fast as possible, spending fewer tokens. /2


Tell me: how many installs does your repo run in a day? 👇 Don't take my word for it, the benchmark is public 👇 🪄 benchmarks.vlt.io/registries… /6

Plus, vlt 1.7 dropped yesterday: ship just ONE workspace + its prod deps into a standalone folder with vlt deploy, ready for your Docker image 🐳 /5

Why does it matter? Because your project doesn't install once. It installs on every PR, every CI job, every branch and every Docker build. A few seconds per install adds up fast across a whole team. And the bigger the tree, the bigger the win: on Babylon.js, the biggest project we test, it's 41.7s vs 51.7s on npmjs.org. That's 10 seconds back on every single install. /4

What changed on the registry: ✅ cut everything until a typical install hits CDN cache and nothing else ✅ stripped package metadata down to what an install actually needs ✅ implemented a fast auth path using stateless tokens ✅ made the metadata of huge packages like next load in ~73ms instead of ~12s /3

4 months ago, vlt's registry was SLOWER than npmjs.org. Then: 36.2s → 17.0s (−53%). And it kept going: 13.3s today vs 17.6s on npmjs.org (32% faster), fastest on every project we test 📈 No magic trick. Just measuring, fixing and measuring again (and getting humbled by the numbers along the way 🤣) /2


Yeah, come and see our newest open-source project. This is a game-changer for @nextjs apps! And leave a 🌟 on the repo 🤘🏻
Nessa era da IA, a sensação é que nem clicar em menus ou navegar em sites não fazemos mais, então nada melhor do que adaptar suas apps pra essa nova era (de graça e com open source na parada) Aqui na @vltpkg lançamos um projeto open source pra fazer qualquer app Next.js ser operável por agentes de IA (WebMCP, MCP e mais) Não sei você, mas eu já estou navegando em sites complexos só com extensões no navegador (ah, acha onde é que faz X, encontra onde está configurado Y) e a velocidade disso é incrível. Então, se você tem algum app em Next.js, testa esse projeto e, claro, né, deixa aquele star maroto na parada (porque deu um trabalhão). Vou deixar aqui no próximo post, mas já me fala aí, você tem usado agentes pra navegar em sites e cortar caminho pra você ou ainda faz tudo manualmente?

🚀 vlt@1.8.0 is here and with it there's no longer need to run a `vlt setup` to start using the vlt CLI as we're now shipping vlt's public npm mirror as the default read-only registry.