tzcsx

I am also experiencing this: ``` Caused by: net.rubygrapefruit.platform.NativeException: Could not start 'npm' at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:27) at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start(WrapperProcessLauncher.java:36) at org.gradle.process.internal.ExecHandleRunner.startProcess(ExecHandleRunner.java:122) at org.gradle.process.internal.ExecHandleRunner.lambda$run$0(ExecHandleRunner.java:80) at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:80) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:79) ... 2 more Caused by:...

Correction: _Every_ build started via IntelliJ UI will fail with this error, if this build creates a new Gradle Daemon instance. If there is a Daemon created by a build...

Yes, ARM mac M2 and download = false. I tried this: ```kotlin tasks.register("doStuffWithNpm") { args.add("do-stuff") val process = ProcessBuilder("sysctl", "sysctl.proc_translated").start() val output = BufferedReader(InputStreamReader(process.inputStream)) process.waitFor() println("configure " + System.getProperty("os.arch") +...

I am still running into this every day. The first build of the day needs to be started outside of Intellij in order to produce a working Gradle Daemon process...

@deepy Good find! I can confirm that either building with Java 17 instead of Java 21 or using Java 21 and starting Intellij from the Terminal via `open -a IntelliJ\...