[moystard]

Nest.js really helps to put a solid structure around Node.js/Express.js projects . I have found the teams much more productive, with strict conventions to help them build solid and scalable backend platforms.

As you mentioned, the Node.js ecosystem is full of specialised libraries to achieve typical use cases such as authentication/authorisation, ORM/persistence, etc. The Nest.js documentation is a great reference as they include a list of recipes for all those common scenarios and how to implement them in a Nest.js backend.

[toqy]

I don't think I've ever had a great ORM experience with node. I inherited a project that was nest + typeorm. I've found nest pretty pleasant but typeorm is buggy and was generating way to many queries for stuff.

[robwg]

This has been my experience as well. I've been happy with nestjs but haven't found an ORM that fully did what I expected. MikroORM seems to lead the way though (I know it isn't the most popular). My main issues with MikroORM could of very well been self inflicted and I ended up writing my own SQL.

[moystard]

I agree that ORMs in the node world do not provide a good experience at this stage, so I mostly go with knex these days.

I had a decent experience with TypeORM after I spent time understanding how it works under the hood to optimise the queries (notably by defining the relationships better).