Cut a release 1.6.0 (or maybe 2.0?)

We've moved to Parcel since 1.5.0 which should open a lot of possible improvements, but also introduces some challenges. This issue is to track known issues we need to resolve/investigate to get to a release:

- [ ] Ensure generated types work
- [ ] This seems to be a bug in Parcel https://github.com/parcel-bundler/parcel/issues/8082
- [ ] Perhaps we can use `tsc` directly? https://www.typescriptlang.org/docs/handbook/declaration-files/dts-from-js.html
- [ ] Especially config object with inline docs
- [ ] For each build
- [ ] Okay if they include private apis (but ideally these are prefixed with _)
- [ ] Ensure we have a build which works with a script tag (global variable)
- [ ] Okay if this is full bundle only
- [ ] This should have minified and unminified versions
- [ ] Ensure we have a version that works with ES Modules
- [ ] Ensure we support a lazy bundle (zip and id3 parsing not included by default)
- [ ] Ensure we have a version that works with TypeScript
- [ ] Ensure we support a lazy bundle (zip and id3 parsing not included by default)
- [ ] Understand bundle-size regression

Start by reviewing the Parcel migration and the linked Parcel issue, then work through the checklist for generated types, script-tag globals, ES Modules, TypeScript support, lazy bundles, and bundle size. Done means the release target is decided and each listed build variant and size regression has been resolved or explicitly accounted for.

Written by the indexing model from the issue text.