🚀 Feature: Make it easy to use across a monorepo

[maelp]

trafficstars

Bug Report Checklist

• [X] I have tried restarting my IDE and the issue persists.
• [X] I have pulled the latest main branch of the repository.
• [X] I have searched for related issues and found none that matched my issue.

Overview

Perhaps there could be a "monorepo-enabled" mode where we would have all the config files in a shared location, and an easy way to update them from the origin repo, so that we can use the best-practices configuration on multiple projects in the monorepo easily, and keep them up-to-date together?

Additional Info

No response

[JoshuaKGoldberg]

🙌 Yes! Monorepo support would be fantastic. I've got several projects personally that either are or will soon be set up as a monorepo, and would love to use create-typescript-app for them.

Do you have any thoughts on what this might look like? How those files might be stored, CLI flags / options, etc.?

[maelp]

Not sure how it would look to be honest, but I'm struggling to create a "state-of-the-art" so-to-say monorepo which would have:

• an expressjs typescript backend
• a vitejs vue3 frontend
• a shared typescript library being included in both the backend and the fronted

it's a mess of ESNext / CommonJS / tsconfig / vite.config options that go out of control, and nothing compiles although everything is valid typescript

if someone could have a basic monorepo like that, with your opinionated setup, it would be really cool!

[JoshuaKGoldberg]

Coming back: #1181 has details on making a create package. I'm going to say monorepo support is out of scope for now, but will be something the create package will definitely tackle long-term. Cheers!