fix: install script not x86 windows; add warning for arm64 windows

[vladfrangu]

What does this PR do?

This PR "fixes" the install script on Windows by correctly checking whether the script is ran on x64 instead of ARM64.

That said, bun does seem to work fine on ARM64, including building bundles but ofc it's probably luck of the draw. Crosscompiling on x64 and running on ARM64 doesn't work however...

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

Ran -not (((Get-CimInstance Win32_ComputerSystem)).SystemType -match "x64-based") on Powershell on Win11 on ARM64

On a friends machine, that IS on x64,

related #9824

[RiskyMH]

Nice, I didn't know bun worked on arm windows. I wonder if it is because microsoft made a decent emulator now or if just really lucky with how the binary is made.

I wonder if we should make it throw a warning though, to tell user that it has a higher chance of random issues.

[vladfrangu]

Nice, I didn't know bun worked on arm windows. I wonder if it is because microsoft made a decent emulator now or if just really lucky with how the binary is made.

The installed bun SEEMS to work, but I've only used it for two things: running a random script, and building a bundle. Building a bundle on x64 and copying it on ARM64 doesn't work however, and I have been unable to debug why...

I wonder if we should make it throw a warning though, to tell user that it has a higher chance of random issues.

If you want, I can do this too for sure! I do wonder what it would take to actually get a native build of bun on arm64 tho 👀 (gh does have windows-11-arm runners now, but I assume its more so JSC/zig stuff?)

[RiskyMH]

So after trying out this windows arm (emulated on apple silicon macbook), I haven't found any clear issues that windows bun in general doesn't already have.

But would like input from @Electroid (or other team members) if should be documented further, just have it working with warning, or block install like this pr will do. Oh and consider building it natively, but that seems to be an interesting task.

[190n]

I'd be fine with allowing Windows ARM as long as we update the issue template to make sure we know when users are emulating it:

For MacOS and Linux: copy the output of uname -mprs For Windows: copy the output of "$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })" in the PowerShell console

Right now I believe this will have WoA users writing x64 since it is 64-bit.

[RiskyMH]

We can edit the script to be a simpler & show the type

"$([Environment]::OSVersion | ForEach-Object VersionString) $env:PROCESSOR_ARCHITECTURE"
# normal: Microsoft Windows NT 10.0.26100.0 AMD64
# arm:    Microsoft Windows NT 10.0.26100.0 ARM64

On this similar thinking, the crash report I'd also like to have it show this too (ie on windows x86_64_baseline (arm emulating) [InstallCommand] type thing), but not sure how hard that would be.

[vladfrangu]

On this similar thinking, the crash report I'd also like to have it show this too (ie on windows x86_64_baseline (arm emulating) [InstallCommand] type thing), but not sure how hard that would be.

If you can guide me where that is done I can try to make it happen, but it might take longer. 😅

[vladfrangu]

Ok, rebase from UI breaks verification. ty GitHub