Feature/es module support

[elpoelma]

Adds support for the installation of es modules in your project.

[elpoelma]

yes indeed

[nvdk]

you may want to change the base to feature/typescript-support to make the diff a bit cleaner. Github will automatically update the base when the other PR is merged

[madnificent]

Indentation changes make it harder to read this PR, regardless of whether or not they should be executed at all.

Is the change in the import statements something that end-users will notice too? We see the import changed from ./server and ./sparql to ./server.js and ./sparql.js or is that an automatic change? Is there a way to keep this consistent with the way the template worked and lower the noise? :-)

[elpoelma]

The .js extensions which are added are IIRC a requirement when using es modules.

[nvdk]

The .js extensions which are added are IIRC a requirement when using es modules.

as per discussion in the chat, this is confirmed by https://nodejs.org/api/esm.html#mandatory-file-extensions . As such we should consider this a breaking feature

[nvdk]

as per further discussion with @MikiDi, I think we could restore/support the old behaviour with babel using this plugin: https://www.npmjs.com/package/babel-plugin-add-import-extension

[Windvis]

If a breaking change is happening with the node 18 bump anyways, would it make sense to include this as well? More and more packages are switching to ESM-only publishing setups.

[MikiDi]

This still would need some work then, right (swapping target to es2022, ...) ? The changes themselves should be easy, but I don't feel confident as a tester for this one.

[Windvis]

(I've opened #63 to discuss the implications and the plan forward.)