Support for ESM

[Dev79844]

Is your feature request related to a problem? Please describe.
The cloudevents package is currently published only as CommonJS. This makes it difficult to consume in native ESM environments (e.g., Node.js with "type": "module" or .mjs files) without additional interop code. Developers must resort to workarounds like createRequire() or transpilation, which adds friction and complexity to using the library.

Describe the solution you would like to see
Publish cloudevents as a dual package that supports both CommonJS and native ESM:

• Retain the existing CommonJS build for backward compatibility.
• Add an ESM build with package.json "exports" and "type" fields set appropriately.
• Ensure the ESM build supports direct imports and works in Node.js, modern browsers, and serverless environments.

[lholmquist]

Is there a problem that you are actually experiencing when adding this to an ESM project.

I was able to just do import {HTTP} from 'cloudevents for example, in a mjs file and also a project where the type:module in the package.json

[Shubham-Thanki]

Hello there @lholmquist 👋
Hope you're doing well !!!

Dev's teammate here, so the thing is we are using the cloudevents in one of our package A, which is then used everywhere. And since we are in a .ts environment and we use tsc --build to build our code, it generates .js files and not .mjs files. So I guess we would face an issue there. (Considering the fact that I have my package set to type: module)

I might be wrong, feel free to correct me if that is the case here.

Thanks in advance !!!