I've had varying degrees of success over the years with various monorepo approaches, and have so far been most happy with pnpm workspaces plus TypeScript project references (plus Changesets when it's necessary to manage changelogs for published packages). oneRepo looks like it combines the things I like best about these tools and solves some additional headaches, so I'm looking forward to trying it out.
[0] https://onerepo.tools/concepts/why-onerepo/#alternatives--pi...
Thank you for the kind words! I had hoped to do a more in-depth feature comparison and review, but it is an incredible amount of work and I'm afraid that I will totally botch it – I've only gotten _so far_ with other tools because of the various pitfalls and workflow/devex show-stoppers that I've hit for me and my teams.