TypeScript monorepo with no extra modules

Don’t Repeat Yourself, project edition

Only a few years ago, having a repository for every project made a lot of sense. That’s because, unless you had a really big company, you were likely to have only a few, completely independent projects.

Your GitHub org structure probably looked like this:

My Company
 - website.git: The repo that houses your web server. This application servers up HTML and responds to GET/POST. It calls out to a database somewhere most likely.
 - backend.git: Ok…