[IDEA] distribute as all module types {CJS,ESM,UMD,AMD}

[jkowalleck]

currently, the package is a CommonJS module type.
I would love to make it a native module type (ESM).

Goal: have the dist available in multiple flavors

• ESM for browser
• commonJS for browser
• esm for node
• commonjs for node
• umd ...
• amd ...
• ... etc ...

Important to READ:

• https://nodejs.org/api/packages.html#dual-commonjses-module-packages
• maybe helps with the missing file extensions when importing: import aliases - https://nodejs.org/api/packages.html#subpath-patterns

implementation:

• use https://nodejs.org/api/packages.html#package-entry-points
• use https://nodejs.org/api/packages.html#dual-commonjses-module-packages
• have multiple TypeScript compilers and webpack runs, that generate isolated JavaScript for each purpose

[agschrei]

are there still plans to produce an ESM for the browser?
I got it to work as an import in my vite project by forking and altering the package.json to:

• skip the webpack step in the build phase
• point to the index.web.js as main

of course I'd rather see support for this use-case added upstream as opposed to maintaining a fork, so please let me know if I can help.

[jkowalleck]

Moin @agschrei,

yes, the idea is still relevant.
feel free to (draft) pullrequest a (partial) solution.

[jkowalleck]

@agschrei are you still interested in contributing your solution?

[eknowles]

I'm not attached to this project but I support this use case. As the front-end industry moves towards ESM for dev builds being able to validate SBOM production as early as possible is very helpful.

[jkowalleck]

This feature is kind of obsolete, now.
There are tests, that show that this library is able to run in ESM context, so no additional work seams to be needed at the moment.
see https://github.com/CycloneDX/cyclonedx-javascript-library/blob/main/examples/node/javascript/example.mjs