I'm pretty language agnostic, but for webstack I like to use Node, because it means I don't have to context switch too hard. I'm using the same language on the frontend and backend with the same APIs. I only have to keep one standard library in my head and a lot of packages are compatible with either front or backend.
Whenever I'm working on the web, that's going to be my go to.
I would consider Typescript, but I don't think the cost/benefit of Typescript really balances out until you have a team. The need to create types and type harnesses for libraries slows you down at first, and speed is the name of the game with an MVP.
I love Django but think this is a pretty sensible stack for a single developer who is strong at JS.
You are still going to have to make a lot of correct library decisions to implement key features like auth and a DAL. Nest JS is an interesting batteries included approach (haven't tried). TypeORM had a lot of issues few years ago but might be getter better.
Disagree re: TypeScript though. Most libraries worth using have types or are TS native these days. I find myself much more productive writing TS on solo projects with less foot gunning.
I went with:
Terraformed AWS/EKS
Docker
Postgres
Node/Express
React
I'm pretty language agnostic, but for webstack I like to use Node, because it means I don't have to context switch too hard. I'm using the same language on the frontend and backend with the same APIs. I only have to keep one standard library in my head and a lot of packages are compatible with either front or backend.
Whenever I'm working on the web, that's going to be my go to.
I would consider Typescript, but I don't think the cost/benefit of Typescript really balances out until you have a team. The need to create types and type harnesses for libraries slows you down at first, and speed is the name of the game with an MVP.