I've done a lot of work with NestJS. I agree with some, but not all, of the authors points.
- TypeORM is pretty bad. Particularly when you start using it for more than simple crud operations. There was an epic battle in the GitHub issues and eventually some folks finally got through to the maintainer. Since then, development has picked up and some long-standing issues have been corrected. It's still pretty bad. However, I haven't found anything in the nodejs ecosystem that's substantially better, which is sad.
- class-validator and class-transformer mostly work, but are barely maintained and have many issues going back years. The maintainers left a bad taste in my mouth. I asked years ago about why these libraries which are so core to NestJS are not forked. The issue was locked with a frustrating response. It sounds like they may have finally been pursuaded to fork them.
- NestJS support is terrible. I understand they have a paid support service but if you don't subscribe to that, they lock, discard, ignore any issues raised, even if they are valid and significant. They push all support questions to Discord, and as far as I can tell, none of the actual maintainers look at it. Very frustrating.
- NestJS breaks semver by releasing breaking changes in minor or patch updates. They don't seem to understand that if a core third party dependency has a breaking change, they need to bump their major version.
- It's very difficult to understand what has actually changed between versions. And with the history of breaking semver, upgrading is just plain scary. The "release notes" are just the commit list, and to make matters worse, they don't use a monorepo so you have to search through a dozen repositories.
Unlike the author, I do actually enjoy the modular design, the dependency injection system, and a few other design choices. The only difficulty I've encountered when testing is around the third party pieces, such as TypeORM.
- TypeORM is pretty bad. Particularly when you start using it for more than simple crud operations. There was an epic battle in the GitHub issues and eventually some folks finally got through to the maintainer. Since then, development has picked up and some long-standing issues have been corrected. It's still pretty bad. However, I haven't found anything in the nodejs ecosystem that's substantially better, which is sad.
- class-validator and class-transformer mostly work, but are barely maintained and have many issues going back years. The maintainers left a bad taste in my mouth. I asked years ago about why these libraries which are so core to NestJS are not forked. The issue was locked with a frustrating response. It sounds like they may have finally been pursuaded to fork them.
- NestJS support is terrible. I understand they have a paid support service but if you don't subscribe to that, they lock, discard, ignore any issues raised, even if they are valid and significant. They push all support questions to Discord, and as far as I can tell, none of the actual maintainers look at it. Very frustrating.
- NestJS breaks semver by releasing breaking changes in minor or patch updates. They don't seem to understand that if a core third party dependency has a breaking change, they need to bump their major version.
- It's very difficult to understand what has actually changed between versions. And with the history of breaking semver, upgrading is just plain scary. The "release notes" are just the commit list, and to make matters worse, they don't use a monorepo so you have to search through a dozen repositories.
Unlike the author, I do actually enjoy the modular design, the dependency injection system, and a few other design choices. The only difficulty I've encountered when testing is around the third party pieces, such as TypeORM.