The best open source projects aren't just about great code. They're about the people behind them. When I stumbled upon npmx.dev at the end of January, I wasn't expecting much more than a cool tool to check out. What I found was one of the most welcoming open source communities I've been part of.
The Discord link that started it all
It all started on January 31st, when someone shared a link to npmx.dev in the LyonJS Discord server (a community server in Lyon, France for JS devs). Back then, the headline read "a better browser for the npm registry". I clicked, and was immediately impressed. The interface was clean, fast, and packed with features I didn't know I needed.
Fun fact: the headline has since been changed to "a fast, modern browser for the npm registry", because the team didn't want to promote the project by putting down existing tools. A small detail, but one that says a lot about the mindset behind this project.
I did what a lot of developers do when they find something cool: I shared it on Bluesky. Barely ten minutes later, patak, one of the core maintainers, reached out and invited me to join the project's Discord server.
awesome! are you at chat.npmx.dev? join if not, you'll surely like the community that is building the tool too ❤️
— patak (@patak.dev) February 2, 2026 at 9:20 PM
I then noticed the project was built with Nuxt. As someone who's been working with Vue.js and Nuxt for years, this was a very welcome surprise. It made even more sense when I realized danielroe, Nuxt's lead maintainer, was behind it.
That's when things started to get interesting.
First PR, first impression
I wanted to get my hands dirty, so I looked for a quick first contribution. That's usually my go-to approach: start with something small to get a feel for the project's workflow and the team's responsiveness. I found a small improvement to make on some tooltips and submitted a PR. Nothing fancy, just a few lines of code. Within an hour, it was merged.
In my experience, contributing to open source usually means submitting a PR, waiting a few days, and maybe getting a review if you're lucky. Here, the feedback loop was almost instant. The project relies on smart tooling to streamline the review process, which makes contributing feel effortless, especially as a newcomer.
At that point, I knew I wanted to do more. I started looking for ways to make a bigger impact.
Lost in translation (keys)
It didn't take long for me to notice that the app's internationalization needed some love. As a French developer, the missing French translations were an obvious place to start. I submitted another PR to fill in the gaps, and that's when I went down the rabbit hole.
While working on the translations, I realized that a lot of translation keys weren't actually used anywhere in the app. That meant other translators could end up spending time translating strings that would never be seen by anyone. So after wrapping up the French translations, I proposed building a script to detect unused keys and run it in CI to keep the translation files in check.
The maintainers were on board, and the PR got merged quickly. This is also where CodeRabbit really shined: automated reviews handled the implementation details, freeing maintainers to focus on the bigger picture. It made the whole back-and-forth much smoother.
Last PR was about actually removing the extra translation keys, and I won't lie, there's something deeply satisfying when the diff is mostly red. Sometimes the best contribution you can make is removing things.
When a project takes a breath
Then on February 13th, the team did something you rarely see in open source: they announced a one-week break.
see y'all in a week 👋
— npmx (@npmx.dev) February 13, 2026 at 10:00 PM
[image or embed]
In a space where momentum is everything and shipping fast is the norm, deliberately hitting pause takes courage. But the reasoning was simple and honest: building something innovative takes energy, and sometimes you need to step back to come back stronger.
The community response was overwhelmingly positive. All Discord channels were locked for the week, except for one: #garden. The name was a not-so-subtle hint to go touch grass. And people did. The channel filled up with pizza pics, nature shots, and photos of danielroe and patak skiing. It wasn't about npmx anymore, it was just people hanging out. That's when it really clicked for me: this community goes way beyond the code.
Meanwhile, the project crossed 2,000 stars on GitHub during the break. We celebrated it on Discord and shared the milestone on Bluesky. When everyone came back, the energy was through the roof. One goal in sight: getting the alpha release ready for March 3rd.
What's next
And here we are. Today, March 3rd, npmx.dev officially enters alpha.
There's a lot more to talk about. The project recently shipped social features that let you like packages using your Atmosphere account, and there are exciting things happening around ATProto and decentralized data. The team even launched a European PDS and invited members to migrate to it. I'll dig into all of that in a future post.
What I want to leave you with is this: if you're looking for an open source project to contribute to, don't just look at the tech stack or the star count. Look at how the maintainers treat their community. Look at how fast they respond, how they handle breaks, how they make newcomers feel welcome. That's what makes a project worth investing your time in.
npmx.dev is one of those projects. Go check it out, and if you're curious, come say hi on Discord. You might just stay for the people.
If you want to follow along with my open source journey, you can find me on Bluesky.
Who knows, maybe your next favorite community is just a Discord link away 👨💻
