fix: add module.exports CJS syntax, add example with require

[aeworxet]

This PR:

• adds module.exports CJS syntax, to maintain backward compatibility with Node.js projects that use CJS module system,
• adds two more examples of code usage written in JavaScript, in addition to the one already provided written in TypeScript.

Fixes #81

[aeworxet]

@magicmatatjahu

[derberg]

@aeworxet you need to fix tests

[derberg]

I just tested with my local project and looks like you can do both:
export default async function bundle and module.exports = bundle;
after transpilation it looks like:

exports.default = bundle;
// 'module.exports' instead of direct export of the function is used, to
// maintain backward compatibility with Node.js projects, that use CJS module
// system.
module.exports = bundle; 

in my code I can do const bundle = require('@asyncapi/bundler'); and it works
and on local tests with import bundle from '../../src'; also work

[aeworxet]

Then I seem to have overengineered a bit.

[magicmatatjahu]

I also tested on my machine and I see:

exports.default = bundle;
// 'module.exports' is added to maintain backward compatibility with Node.js
// projects, that use CJS module system.
module.exports = bundle;

and it works for ESM and CJS 🚀

[magicmatatjahu]

Two changes :)

[derberg]

@aeworxet please do not do force-push

• it is hard to check what you changed and reviewer needs to go through entire PR again
• GitHub Actions do not like it, and as you can see tests were not triggered

[magicmatatjahu]

LGTM! :)

[magicmatatjahu]

@derberg ping :)

[aeworxet]

Summoning @Souvikns

[Souvikns]

👍🏼

[derberg]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.3.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀