Change runtime to bun

[KaiVolland]

This changes the runtime and creation of the binaries from node to bun.

It also adds options to read ArcGIS styles via geostyler-lyrx-parser.

⚠️ As this changes the runtime of this project this will result in a new major version.

[marcjansen]

Are the changes to the installation guide (or the part usage without installation) in the README needed? It will still be possibly to run this CLI without bun, or not?

[KaiVolland]

Are the changes to the installation guide (or the part usage without installation) in the README needed? It will still be possibly to run this CLI without bun, or not?

I was not able to get the module resolution working with node and the current state of the geostyler packages. For some reason node has issues resolving relative pathes in the node_modules. bun seems to be smarter here.

I also struggle validating npx and bunx without publishing the package. 🤔

[geographika]

I only learnt of bun at the codesprint, so I've no useful opinion on switching from one to the other. However, if it addresses #393 then I am all for it!

[jansule]

You also might want to rephrase your commit messages so that the support for openlayers does not appear in the changelog

[marcjansen]

Are the changes to the installation guide (or the part usage without installation) in the README needed? It will still be possibly to run this CLI without bun, or not?

I was not able to get the module resolution working with node and the current state of the geostyler packages. For some reason node has issues resolving relative pathes in the node_modules. bun seems to be smarter here.

I also struggle validating npx and bunx without publishing the package. 🤔

I am +0 on the change of the runtime, so not blocking.

I really would like to stress that installation via node / npx should still work even after we switch to no longer using or endorsing them. Maybe you can create a prerelease and test this?

[KaiVolland]

Are the changes to the installation guide (or the part usage without installation) in the README needed? It will still be possibly to run this CLI without bun, or not?

I was not able to get the module resolution working with node and the current state of the geostyler packages. For some reason node has issues resolving relative pathes in the node_modules. bun seems to be smarter here.
I also struggle validating npx and bunx without publishing the package. 🤔

I am +0 on the change of the runtime, so not blocking.

I really would like to stress that installation via node / npx should still work even after we switch to no longer using or endorsing them. Maybe you can create a prerelease and test this?

After this change, node' and npx' will no longer work.

[ahocevar]

Isn't this a change more radical than it needs to be? Using bun to create the standalone binaries is fine. But what's the benefit of getting rid of a build that works with node? I just created #407, by creating a single javascript file that runs fine everywhere, using rollup. There's no need to get rid of node support, while still being able to use bun.

[KaiVolland]

This is superseeded by #407. I'll create a new PR with the changes that are still useful later.