3 ms·
I would go with NestJS and TypeORM on the backend with node..
by Rapzid 8y ago
I would go with NestJS and TypeORM on the backend with node..
- ludwigvan 8y agoThank you, I will have a look. How mature are those currently?
- jhanschoo 8y agoNestJS was not very mature when I tried it out early last year, and did not support GraphQL then. Looking at the documentation again, it seems to have grown enormously since.
- krzkaczor 8y agoCurrently, I started my very first project using NestJS and it's great. TypeScript support is top notch. DI is amazing. There's is already a lot third party plugins and resources https://github.com/juliandavidmr/awesome-nestjs https://github.com/juliandavidmr/awesome-nestjs
- subsection1h 8y agoNest has a bus factor of one[1]. Django[2] and Rails[3] don't have this problem. [1] https://github.com/nestjs/nest/graphs/contributors https://github.com/nestjs/nest/graphs/contributors [2] https://github.com/django/django/graphs/contributors https://github.com/django/django/graphs/contributors [3] https://github.com/rails/rails/graphs/contributors https://github.com/rails/rails/graphs/contributors
- Rapzid 8y agoDo you mean that nestjs has one developer working on it? It does have one super active Dev, but also a few sponsors that would probably see development continue. Just talking about node/Typescript though.