🔀[build] Port build script to windows

[Cr4zyc4k3]

What kind of update does this PR provide? Please check

• new translations / updated translations / translation fixes
• a new feature
• a new module
• a bugfix for an existing feature / module
• improvement of style or user experience
• other: Please fill out

What is included in your update?

• Port build/build.sh to windows powershell script

[Cr4zyc4k3]

@deoxis9001 It now works on powershell in a default powershell on my system 🙈
Fyi: Currently the --port command is not working so you need to adjust it in the script if you want to use another port than 36551

[deoxis9001]

is it possible to delete these messages locally?

[Cr4zyc4k3]

Probably yes, but the effort would be much higher than the result.

The quick&dirty solution:
For the branches should be an empty branches.json file in the dist folder enough to remove this error.
For the release notes is a deeper inspection required.

@jxn-30 Thoughts on this topic?

[jxn-30]

Probably yes, but the effort would be much higher than the result.

The quick&dirty solution: For the branches should be an empty branches.json file in the dist folder enough to remove this error. For the release notes is a deeper inspection required.

@jxn-30 Thoughts on this topic?

empty branches.json seems fine to me, maybe we could also provide empty Releasenote-Files or otherwise download them similar to the mission files in the prebuild step.

[deoxis9001]

I have other errors

[kdev]

Bun introduced a cross-os shell layer to.
Maybe it's worth a thought rewriting the build script in JS/TS with some sort of compile layer to make it run on multiple OS.
This would require a complete rewrite of the build script but would help maintainability a lot (something this project needs!).
Any thoughts?

Edit: Bun is not the first to introduce something like this. Google open-sourced a similar project years ago.

[jxn-30]

Bun introduced a cross-os shell layer to. Maybe it's worth a thought rewriting the build script in JS/TS with some sort of compile layer to make it run on multiple OS. This would require a complete rewrite of the build script but would help maintainability a lot (something this project needs!). Any thoughts?

Edit: Bun is not the first to introduce something like this. Google open-sourced a similar project years ago.

I like the idea. That may also be useful for #2884 where currently weird child processes are spawned instead.

[Cr4zyc4k3]

Since google is famous for throwing project under the bus (https://killedbygoogle.com/) I won't relay on something they maintain. But I like the idea in general. Until this is done we should keep both versions.

[kdev]

Since google is famous for throwing project under the bus (https://killedbygoogle.com/) I won't relay on something they maintain. But I like the idea in general. Until this is done we should keep both versions.

Luckily they state that it's not a "supported Google product".
I guess they won't throw it under the bus since they are probably using it themselves (also the project is at v7 and has been around for a while now)
Anyways Google's zx is made for just linux scripts so it won't fit our use case.

@Cr4zyc4k3 what do you think about the Bun project?

[Cr4zyc4k3]

If it is possible to accomplish this without installing bun globally I'm cool with this solution.

[Cr4zyc4k3]

is it possible to delete these messages locally?

Should be fixed with 16c51fd

[kdev]

Bun now supports windows. Maybe we should consider switching/rewriting for better maintainability?

[jxn-30]

I think at that point we should take the chance and have a look at the whole CI and see where we could improve it.