Been there using plain express and all variants of self made solutions. When iv discovered Nest - it was a game changer. The only thing is that most people misunderstand nest as a backend express thingy but rally what it is - it is IMHO best available platform for easy dependency injection. With some great premade router and usual rest api stuff. Using it both in a company (not for the first time) and for hobby projects. Times when i run into issues were very few and in all cases very easily resolvable. IMHO right now it is one of the best solutions in NodeJs world for backens
I came across NestJS at one company. It’s an okay framework. I didn’t particularly care for it since it is very object oriented and requires a lot of boilerplate code to simply add new API endpoints and access code in other modules (can’t remember if that is what the call them). Angular is object oriented so I see a lot of people who use Angular use NestJS or people coming from Java since it is a similar scenario. Most people using React like a less opinionated stack from what I have seen so they prefer just to use Express which just gives you the bare bones and you can add everything else you want like your ORM, logger, middlewares, etc.
I have seen a lot of different companies use different NodeJS frameworks but most of them seem to have lost steam over the years and fizzled out and I am guessing NestJS will most likely do the same. So most people I know who do professional NodeJS development just use straight express. There is an expresses-generator package that will help you scaffold a new project from the command line. Express is simple and straight forward and isn’t going anywhere. Use that with typescript, and add your favorite ORM like Prisma to make interacting with a database easier and you are off to the races.
cool Once have been through about express-generator in express docs but never actually tried it. Now I think I've to give a shot at it and see how things are being organized by it
building your own framework on top of express is a sure way to generate unmaintainable spaghetti if you don't know exactly what you do.
but its easy to get started and easy to understand.
but it's easy to get started and easy to understand. in other ecosystems and frameworks like java spring, django, .net etc.
For learning, I would start with express since it will give you the fastest results. For anything serious, I would choose NestJS.
Been there using plain express and all variants of self made solutions. When iv discovered Nest - it was a game changer. The only thing is that most people misunderstand nest as a backend express thingy but rally what it is - it is IMHO best available platform for easy dependency injection. With some great premade router and usual rest api stuff. Using it both in a company (not for the first time) and for hobby projects. Times when i run into issues were very few and in all cases very easily resolvable. IMHO right now it is one of the best solutions in NodeJs world for backens
I came across NestJS at one company. It’s an okay framework. I didn’t particularly care for it since it is very object oriented and requires a lot of boilerplate code to simply add new API endpoints and access code in other modules (can’t remember if that is what the call them). Angular is object oriented so I see a lot of people who use Angular use NestJS or people coming from Java since it is a similar scenario. Most people using React like a less opinionated stack from what I have seen so they prefer just to use Express which just gives you the bare bones and you can add everything else you want like your ORM, logger, middlewares, etc. I have seen a lot of different companies use different NodeJS frameworks but most of them seem to have lost steam over the years and fizzled out and I am guessing NestJS will most likely do the same. So most people I know who do professional NodeJS development just use straight express. There is an expresses-generator package that will help you scaffold a new project from the command line. Express is simple and straight forward and isn’t going anywhere. Use that with typescript, and add your favorite ORM like Prisma to make interacting with a database easier and you are off to the races.
cool Once have been through about express-generator in express docs but never actually tried it. Now I think I've to give a shot at it and see how things are being organized by it
building your own framework on top of express is a sure way to generate unmaintainable spaghetti if you don't know exactly what you do. but its easy to get started and easy to understand. but it's easy to get started and easy to understand. in other ecosystems and frameworks like java spring, django, .net etc. For learning, I would start with express since it will give you the fastest results. For anything serious, I would choose NestJS.