Runtime agnostic - Support non-Node.js runtimes

[MickL]

This package is clearly named "-node" but I wonder if it uses Node specific imports or if it runs in other runtimes, too. E.g.:

• Bun
• Deno
• Serverless workers / Edge workers (Amazon Lambda, Cloudflare Workers, etc.)

What I would expect:

• If it is already platform agnostic, add this info to the readme/docs and rename the package e.g. mollie-api-javascript
• If it is not, try to make it work with web standards (e.g. use fetch) and treat Node specific behavior as an exception.

IMO all libraries should aim to be platform agnostic. E.g. Bun outperforms Node and sticks to web standards. Also serverless (edge) functions are a very common usecase in modern architecture. Especially Node has some quirks that are Node specific and not web standard, so personally I would treat Node more as an exception than the standard. E.g. an API developed with something like H3/Nitro runs/deploys "everywhere" but would then possibly fail using mollie-api-node.

[janpaepke]

This is a reasonable request, which has been discussed before in #208 and #278.
The reason those have not yet been picked up is not because we oppose in principle but because of lacking priority / urgency.

Feel free to weigh in on the mentioned discussions, should you feel this is currently underrepresented.

[MickL]

To have more companies use Mollie itself, you should prioritize developers needs which are building the software of the future. If they see that Mollie is not suitable for their tech stack, e.g. if they decided to leave Node behind and go runtime agnostic, they will discuss with their stakeholders to use other services instead.

Personally I think the two issues that you linked are too specific. They target Cloudflare Workers and Bun. Instead this is a general issue: Remove Node dependencies, use runtime agnostic packages (e.g. the ones from UnJS) and it will run everywhere.

I would kindly ask to reopen this issue, and make the other two sub issues of it.

[janpaepke]

agreed.