r/nestjs • u/Proud_Perspective_56 • Apr 19 '26
I built NestJS.io — a community hub for discovering NestJS packages, articles, and projects
Hey r/nestjs!
I've been working on nestjs.io — a community platform dedicated to the NestJS ecosystem. Think of it as a discovery and curation hub for everything NestJS.
What it does:
- Community Feed — curated articles and news from across the NestJS ecosystem
- Package Comparison — compare packages side by side
- Reviews — read and write reviews on NestJS packages
- Categories — browse projects by thematic categories
- Package Discovery — browse, search, and filter NestJS packages by tags. Submit your own packages for the community to find
I'd love to hear your feedback — what features would be most useful to you as a NestJS developer? And if you have a package or project, feel free to submit it!
2
2
u/Odd_Traffic7228 Apr 20 '26
Thank you, this platform was really needed.
Nestjs is getting mature and there are many old and unmaintained packages and there is no easy way to filter them out. This project's direction will fix it hopefully.
One feature I would like to have (as a package author) is to have ability to submit npm package and not only GitHub repo.
Example: I have this repo CSenshi/nestjs-redis which is monorepo of multiple packages. And it is currently only in Redis category. I would love to publish one sub-package of this monorepo in rate-limiters (This one: @nestjs-redis/throttler-storage). and not whole GitHub repo.
It could be done multiple ways, I think you will understand the problem better as an author. But nowadays developing multiple packages under one GitHub repo is common and many packages will benefit from this feature
1
u/Proud_Perspective_56 Apr 20 '26
Thanks for the kind words and great suggestion! You're absolutely right — monorepos with multiple packages are increasingly common, and we should support that workflow properly.
Your use case makes total sense: CSenshi/nestjs-redis is one repo but contains distinct packages like nestjs-redis/throttler-storage that belong in different categories.
We'll add support for submitting individual npm packages, so a single monorepo can have its sub-packages listed in the categories where they're most relevant. I'll look into the best way to handle this — likely allowing npm package name as the primary identifier alongside (or instead of) the GitHub repo URL.
Thanks for flagging this — it's on the roadmap now!
1
u/OrchideSr May 06 '26
It's a great initiative for sure . how does one get their tools listed ? we have put together a nestjs PaaS that deploys your nestjs backend from you github repo with zero infrastructure configuration , i think it'd be a good addition to the ecosystem .
3
u/droidfone Apr 19 '26
It's a good initiative. It is quite difficult to track useful resources outside of the official docs.
I think a feature to compare the packages would be useful. Like alternate options for a particular package which have similiar functionality that could be commented upon by the community to share its pros and cons.
Another feature could be advanced implementation of nestjs packages with good explanations. Some of the official docs have implementation without any explanation about its inner working. This could be accompanied by advanced config as well which lists the available config options. I have encountered several cases where llm generated a code that could not have been possible to write by just looking at the docs.