build ESM dist for npm package

[turadg]

A recent conversion of a lib file to .ts broke downstream deep imports of it.

This builds .js files in the distribution and prevents deep imports.

[mhofman]

Let's add an exports field to prevent external users doing deep imports into dist

[turadg]

I was reluctant to make that big a change yet, but I suppose consumers that it would break just won't upgrade.

However, it's for an additional improvement over the status quo. While it's good, it's not necessary to unblock the issue you raised. Can you wait for this to be future work?

[mhofman]

it'll break consumers already with the move, might as well make it official. Introducing exports is technically semver major, might as well bite the bullet once

[turadg]

It's in ba21b9f

414dcf6 had broke CI because I made the proposals stop using deep imports too, but they're using older release so I backed that out and force-pushed. It doesn't affect what's in 0.0.6-3.

[mhofman]

Given the move / introduction of a dist folder, I would strongly prefer if the package.json added an exports field.

[mhofman]

Let's sync on supporting tests like Agoric/agoric-sdk#8786 and Agoric/agoric-sdk#8787

[mhofman]

Can we generate d.ts.map as well? Going to implementation is broken in VS Code without it.

[mhofman]

Ugh apparently it's a limitation: egoist/tsup#564

[mhofman]

Actually, it shouldn't be necessary here, I'm confused why go to definition is not working for me

[mhofman]

I have confirmed this works in an agoric-sdk branch!