Today, npmx.dev officially enters alpha: a fast, modern browser for the npm registry. We've been watching this project closely at VoidZero, because npmx is built on our toolchain and feedback from its developers has already made our tools measurably faster. Here's how that relationship works.
A shared mission
VoidZero's mission is to make JavaScript developers more productive than ever before, including how developers find and choose packages. That's exactly what npmx is tackling. Beyond browsing packages, npmx surfaces details that help you decide which package to adopt in your project: package sizes, performance recommendations, outdated dependency warnings and more.
Shipping fast with VoidZero's tools
What makes this relationship especially exciting is that npmx doesn't just share our vision, it is also built with our tools. The npmx.dev codebase runs on the full VoidZero toolchain:
- Vite as the build engine via Nuxt, giving the team instant HMR during development and optimized production builds
- Vitest for the test suite, with consistent transforms and config shared from the Vite setup
- Rolldown through the Vite 8 beta, producing smaller, faster production bundles
- oxlint for linting that runs in milliseconds, even across the full codebase
- oxfmt for consistent formatting with near-zero overhead
The npmx team has also been using a preview release of Vite+, the unified toolchain composed of all the above tools in a single package.
A feedback loop that benefits everyone
The folks building npmx are real builders and maintainers from across the JavaScript ecosystem. When they use our tools day-to-day, they hit edge cases and surface issues that synthetic benchmarks and internal testing simply can't. Running on cutting-edge builds means they catch rough edges early: from unexpected performance regressions to configuration quirks that only show up in production-scale codebases.
One concrete example:
- An npmx maintainer noticed that
lintandfmtwere unexpectedly running postinstall scripts, making Vite+ commands over 3x slower than calling oxlint and oxfmt directly - They filed the issue with concrete benchmarks from the npmx codebase
- We fixed it, and the overhead dropped from 3.23x to 1.10x
That's the kind of real-world signal that makes our tools better for everyone.
npmx is an open-source project fully developed by volunteers. They adopted our tools because they are fast and provide a great developer experience. They push our tools to their limits, and it helps us make them better. To make sure npmx can keep pushing forward, we started sponsoring the project and are excited to see where they take it next.
This is what a healthy open-source ecosystem looks like: independent projects pushing each other forward. npmx helps developers find better packages, and their real-world usage helps us build better tools to create them with. Check out npmx.dev and see for yourself.
This post is part of the npmx alpha announcement web ring. Read the official announcement on the npmx blog and discover more perspectives from the community.