Nest.js + Angular on the frontend is a dream. Nest.js was modeled after Angular and they both use a similar basket of concepts/tools (dependency injection, decorators, first-class TS support). You can build a robust full stack app without context switching. They are both opinionated, ensuring a consistent and predictable structure.
If you go the Nest + Angular route, I recommend checking out NX monorepos, which adds another level of seamlessness. NX was created by former Google/Angular team members. One of my favorite features includes the ability to easily share libraries/models across the front end and backend. E.g., if you're designing an API, you can import the same model file to both the front end and back end, ensuring no divergence between both sides as the API is redesigned.
> One of my features includes the ability to easily share libraries/models across the front end and backend. E.g., if you're designing an API, you can import the same model file to both the front end and back end, ensuring no divergence between both sides as the API is redesigned.
To be fair this applies to any case where you have the same language on the front and back, which was one of the main motivations for Node in the first place
If you go the Nest + Angular route, I recommend checking out NX monorepos, which adds another level of seamlessness. NX was created by former Google/Angular team members. One of my favorite features includes the ability to easily share libraries/models across the front end and backend. E.g., if you're designing an API, you can import the same model file to both the front end and back end, ensuring no divergence between both sides as the API is redesigned.