ESM entrypoint isn't functional

[acidoxee]

The files in dist/esm are not valid ESM because:

• The folder is missing a package.json with { "type": "module" } in it, OR files use a .js extension instead of .mjs (since the closest package.json states the package is using CJS)
• Relative imports in those files don't have an extension

This causes esbuild (for my case) and maybe other bundlers to discard this entrypoint and fallback to the CJS one instead (TypeScript resolution also points towards the CJS entrypoint, even when consumed from ESM code).

Do you think you might be able to fix the entrypoint to make ESM code able to consume ESM from your package as well? 🙏

[Skn0tt]

Thanks for reporting this! This sounds like a regression to me. I’m not in office until beginning of next week, but will take a look then.

[Skn0tt]

Released a pure ESM version in https://github.com/blitz-js/superjson/releases/tag/v2.0.0, let me know if that works for you!

[acidoxee]

I'm currently assessing whether this breaks something or not in my app, but what's sure is that esbuild now properly leverages ESM for superjson and its dependencies 🥳

I believe going ESM-only is the right move for most libs, otherwise people would rarely have any real incentive to move away from CJS. Anyway, thanks a lot for your quick reaction and fix! I'll open another issue if I stumble upon other problems.