Benoit Sautel

Ok, so you mean that the issue happens only when running an arm64 JVM. If you run a x86 one using Rosetta 2, you don't encounter the issue, right?

Ok, that's interesting. We use the Gradle exec API to execute `node`, `npm` and `yarn`. So either the issue is in the Gradle exec API implementation but I assume this...

Ok, thanks for your feedback @alexpartsch. Unfortunately this experiment did not enable us to spot the origin of the issue but that's quite a good news there is not a...

Just to be sure I understand what is happening here. We detect that the system is a macOS running on a arm architecture but the corresponding Node.js bundle does not...

Is it more complicated than returning `darwin-x64` if OS os `darwin` and platform `armxxx` (I don't know what the exact arch code is for Apple M1 systems)? You mean you...

Can someone tell us what the `os.arch` Java property contains when running Java on macOS using a M1 CPU? I am pretty sure that we can fix that quite easily...

I changed the platform detection behavior to return `x64` when running on a Mac with `aarch64` architecture in the `apple-silicon` branch. Could someone with a Mac M1 test that please?...

Thanks for you quick answer. Our integration tests are unfortunately very unstable. That sometimes the case on my laptop but it happens much more frequently in GitHub Actions. That's really...

Thanks @seregamorph for your confirmation that the download now works and for the working directory issue report. It don't really see why an architecture change would lead to break this...

The current working directory variable seems to be right. 🤔 In issue #152 we discovered that the issue related to the `PATH` commands that does not seem to be found...