Goals
- Provide a clean and maintainable monorepo structure for Express.js using TypeScript and Turborepo.
- Help backend-only teams adopt Turborepo to organize multiple Express apps and shared packages.
- Improve the developer experience for Express.js development in a monorepo with shared utils and unified build/dev tooling.
Non-goals
- Not requesting frontend integration (no React, Next.js, etc.).
- Not focused on full-stack SSR or frontend-backend shared rendering.
- Not addressing deployment strategies in this feature request.
Background
Turborepo is a fantastic tool for monorepos but mostly targets frontend use cases. Many developers (like me) want to organize Express.js backends — possibly multiple microservices — inside a monorepo, without needing any frontend tooling.
Right now, it’s hard to find a good, official, or community-backed example of an Express.js-only monorepo setup using Turborepo.
Common pain points:
- Lack of consistent structure for Express in Turborepo.
- Manual setup of shared
tsconfig
,turbo.json
, and scripts. - No reference for using tools like
tsup
,nodemon
, orts-node-dev
.
Proposal
Create a starter example or template for Express.js monorepos using Turborepo, with a structure like this: