In the past years, I have developed numerous applications using NestJS, which have been utilized by hundreds, thousands, and even millions of customers throughout Europe. These applications were…

BtrProg offers insights into software development best practices, algorithms, and data structures, providing tutorials, articles, and coding challenges to help developers improve their programming skills. By exploring BtrProg's curated content, developers can learn about algorithmic problem-solving techniques, data manipulation strategies, and code optimization methods for writing clean, efficient, and maintainable code. Whether you're preparing for coding interviews, honing your competitive programming skills, or simply sharpening your coding prowess, BtrProg offers resources to level up your programming game.

Better Programming

This post discusses the good, the bad, and the ugly aspects of NestJS, including its value for teams, potential issues, and testing complexities.

NestJS: The Good, The Bad, and The Ugly

awesome article we need more of this

After suffering through numerous backends that all ‘knew better how to do it’, working with NestJS has been such a joy. Yes, it’s quite opinionated and has a bunch of things to set up in advance - but maintaining the code, if properly modularized from the start, is so much nicer. Plus the heavy use of decorators helps keeping things clean (provided one likes decorators)

I develop NestJS microservices everyday and I never noticed that points. Except the fact that documentation is really good and complete and new teamates onboarding is really easy.
Good article.

In my opinion, Nest.js does have some problems with customizations and whatnot, but problems, such as the circular dependency, can be worked around through common patterns (mostly with the usage of interfaces and whatnot). And yes, I know this kind of breaks the model Nest.js is trying to go for, but it can be solved without too much trouble.