Migrated build system to tsup

[mattpocock]

Also contains work in #569, merge that first.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d542050

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dmmulroy]

@mattpocock could you please add some context to why tsup is a good/better solution beyond just being "modern"? Thanks!

@supermacro @m-shaka I am a fan of tsup and in favor of this change once justification and context is added to the description

[mattpocock]

The main appeal of tsup is that I trust the declaration files it generates. It also generates one per output type by default (which is recommended by Andrew Branch of the TS team) which means the exports map can be simpler.

If you're happy with your current rollup-based setup, that's fine - but it seemed a bit custom and funky so I thought a low-config, well-maintained option would make sense.

[supermacro]

refraining from diving into this PR until convo for #569 is clarified.

[jalavosus]

@supermacro It appears that #569/#618 were merged. Any chance you could circle back to this?