build: split into monorepo with separate packages

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing issue: fixes Turn into a monorepo #1341; fixes Curious on your thoughts / comparison of TypeStat to ts-migrate? Room for both? One or the other? #1317; fixes Tooling: Migrate to create-typescript-app@1 #1318
• That issue was marked as status: accepting prs

Overview

Splits the large general-purpose TypeStat package into two:

• ts-enhance: Improves a project's TypeScript code by creating and improving types. 💗
• ts-initialize: Converts a project from JavaScript to TypeScript in as few changes as possible. 💝

It additionally publishes a typestat-utils package for shared code.

Generally onboards to create-typescript-app too. I figured this was a good time to do it, and test out what a monorepo with CTA would look like.

Checklist to un-draft:

• Figuring out package naming
• Splitting out package responsibilities
• Finalize setting up workspace tasks and TSConfig project references
• Passing build
• Some passing tests
• Figuring out monorepo/repository naming
• Resolved created TODOs (especially around shared utils)
• All passing tests
• Trying it out as a package
• Discovered issues from ☝️
• One final docs + proofreading push

[JoshuaKGoldberg]

I'm going to work on turning https://github.com/JoshuaKGoldberg/emoji-blast into a monorepo (JoshuaKGoldberg/emoji-blast#172 -> JoshuaKGoldberg/emoji-blast#206) first to try out the tooling in that repository first. Then once that's done and stable, I'll take its learnings here.

[JoshuaKGoldberg]

This is second in line for monorepo conversion. https://github.com/JoshuaKGoldberg/create is first in line and WIP.

[rubiesonthesky]

I have looked little bit into this new structure and I think it's improvement. It makes it more clear what goes with what than current structure.

Only "worry" that I have is, that the typestat-utils package won't have much content. I think in some places it would make more sense to not use some of those helper methods like pluralize, isNotUndefined (this could be replaces with .filter(x => !!x) in newer typescript)) etc.

So maybe the utils package would be more like cli package? So it would contain all things for printing to console, prompting etc? Not sure how viable that is but I kinda would like to see separation from the "business" logic and from the CLI logic in the packages. That would make some testing easier and maybe allow using these tools programmatically :)

I know that you probably want to use this repo as a testing ground for the monorepo migration, but I think that the new file structure that you have here, could be beneficial even before actually creating the monorepo. What I mean is, that the files could be moved under those package name directions how you plan them to be. And then later the whole project could be turned into monorepo.

However, it's exciting to see how you do this change with the tool!

[rubiesonthesky]

I think tsconfig.tsbuildinfo should be added to .gitignore :)