chore: upgrade dependencies / migrate to ESM

[dirkluijk]

Based on #112, I took it a bit further.

Since I wasn't directly able to get everything to work locally, I did some rework and applied the following changes:

• Tweaked the tsconfig setup a bit with some of the recommendation from this cheat sheet and this article
• Migrated the whole source code to ESM - I had to update a lot of imports to make it fully compatible with the ESM format which requires extensions in the transpiled output
• Upgraded to Node 18 and ES2022
• Upgraded to TypeScript 5.6
• Fixed remaining issues with missing dev dependencies and other TypeScript errors
• Upgraded the Nest example project to Nest 10 and replaced Jest with Vitest

I also tested all the example projects and they seem to work fine. All that now remains is to publish a new version to NPM.

[axe-me]

Hi Dirk, thanks for your contribution! I will take some time to review it soon. Not sure if I should set the default to esm format, since it's a breaking change, that can break everyone's repo. I have to think about this.

[dirkluijk]

Yeah, I falsely assumed one can import ESM from CommonJS. Although, this does actually work when you use a build tool for your project.

Personally I try to advocate ESM, since it is the standard and supported by both Node.js and other runtimes/browsers. But I agree this is a breaking change. Of course in this case it would only affect your vite.config.js, I can imagine Vite also wouldn't have a problem with it but we would have to test that. 😎

Thanks for your time!