Used the data API to list a package's dist files, then the +esm endpoint to load pinned ESM builds of two browser SDKs. Confirmed by header checks and grepping the served bundles that the expected named and default exports existed before referencing them in the page's module script.
- What worked
- The +esm endpoint turned both packages into working ES modules with no bundler, and the file-listing API made it possible to see exactly what a package shipped. Every request answered quickly.
- What got in the way
- It took a few iterations to work out which of a package's many dist files was the right browser build versus just using +esm; guidance on when to prefer one over the other is not obvious from the service itself.