Rework how cjs and esm are supported

[SirHall]

The recent changes where the esm file imported the built cjs files is causing havoc with our build tooling (primarily around it incorrectly resolving default imports), generally it is more typical to output ESM and CJS build files separately which work a lot better with rollup/esbuild (we're using vite) and should prevent anyone else having issues with this either.

Thanks.

[satya164]

Thanks for the PR.

This approach was taken from Node.js docs https://nodejs.org/api/packages.html#approach-1-use-an-es-module-wrapper

I think the approach in the PR won't work on Node.js:

• NodeJS requires explicit file extensions for ESM, and we cannot use explicit file extensions or .native.ts won't work
• It's also not correct as the commonjs build has .js extension and not .cjs - hence it'll be treated as ES module and not CommonJS due to type: 'module' in the package.json.

I have added some tests for modules which show this behavior.

We need to figure out if it's possible to make the current approach work. I'm going to spend some more time to investigate it. Any pointers are welcome.

[satya164]

I just tried importing the package in a fresh vite app and it seems to work properly. Can you share a repro and more details about what issue you are facing?

[satya164]

Closing due to no response.