Using Mitosis with Monorepo Tool (like Turborepo)

Looking to build a basic component-library using Mitosis that I would like to eventually distribute to internal users. If I wanted to leverage a monorepo tool to manage all the different packages, could I still use Mitosis?

Essentially, I want the Mitosis output to _be_ the different target library packages that would then be published for download. I'm new to Mitosis so I could be thinking about this the wrong way entirely so feel free to course correct my thinking if it is.

No files, tests, or entry points are named. Start by reviewing Mitosis's package-output configuration and the requirements for a Turborepo-style monorepo, then clarify whether generated target packages can be published independently. Done means documenting a supported package and monorepo workflow, or identifying the concrete changes needed.

Written by the indexing model from the issue text.