Test build output before publishing

[fubhy]

@tim-smart How about this? It's not a silver bullet, but it'd help detect potential issues with the build output. Since this only runs on changeset publish, it'd also not slow down our pipeline elsewhere.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f9473e9

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

[fubhy]

This assumes that some tests import from the root entrypoint. Which, I must admit, aren't that many.

Another option could be to generate snapshot tests for the exported symbols of all public modules. Basically just "dialing in" the public interface in a generated test case.