[aswerty]

I'm literally in the middle of spending my evening, outside of work, gutting NestJS from a project I've inherited at work. I would literally consider changing jobs if I couldn't remove it.

There is so much to unpack to get as why I have such an issue with it. But time and again I have been frustrated with it in terms of: it's design philosophy, implementation, scope of what it covers, bloat, recommended implementation approaches, etc.

I don't understand how a single framework can think that it should cover: message/request handling, logging, config management, dependency inversion, persistence, and IO. These things have almost no cross over (i.e. if they are well designed they should be easily composable with any other component) but time and again framework developers attempt to bundle them into a "one size fits all solution".

To best sum it up. I think any package I use should be secondary to my application. But this package makes it so that my application is secondary to the framework.

[jzig]

Don’t .NET and Rails do all those things?

[NicoJuicy]

They provide a default.

I suppose in nextjs it's the only option?

[ganduG]

Nah, you can swap out most things.

[everybackdoor]

This is about NestJS, not NextJS.