All-in with TypeScript, on both ends: back with NestJS and front with Angular.
How do you organize the serverless functions and frontend code in Git?
A single repository with nestjs and angular folders, a shared folder with interfaces and other overlapping classes and from there the organization of new files and scripts would be made on a case-by-case basis (i.e. what's cross-cutting or application-specific.)
I'd organize serverless function code in the nestjs folder as they'd all likely just wrap the application in a cloud specific way (an AWS wrapper, an Azure wrapper, etc.) and have their respective build/deploy scripts there, too.
Awesome, thank you for sharing!
Do you have a starter repos I can reference to get this going, this is exactly what I am working on?
While not exactly, I have a monorepo (github.com/METACEO/monorepo-example) that shows a structure that I use to achieve the above.
Depending on my cloud provider, I'll write top-level scripts to help with development, deployment, etc. (all of which I hope gets much easier with Bazel.)
Tailoring this monorepo to something cloud-specific probably deserves it's own write-up beyond a comment.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.