Find npm in wrong place

[rhdtl78]

Related the document, plugin have to find npm on global scope, but it is not.

Caused by: org.gradle.process.internal.ExecException: A problem occurred starting process 'command 'npm''
at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241)
...
org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
...
Caused by: java.io.IOException: Cannot run program "npm" (in directory "~/projects/projectRoot"): error=2, No such file or directory

So, I tried to override npm or node excitable path but no effect

My environment is like below.

os.arch = aarch64
os.name = Mac OS X
os.version = 11.2.2
openjdk version "11.0.10" 2021-01-19 LTS
OpenJDK Runtime Environment Zulu11.45+27-CA (build 11.0.10+9-LTS)
OpenJDK 64-Bit Server VM Zulu11.45+27-CA (build 11.0.10+9-LTS, mixed mode)

node -v
v15.10.0
process.arch: arm64

[bsautel]

I confirm that by default the plugin uses the npm command available in the PATH and it is how I use it. The integration tests ensure that we do use the globally or locally installed node and npm commands according to the configuration and they run on both Windows, macOS and Linux. You are probably in a really specific case.

You will probably think that my question is stupid but I ask it anyway: is npm available in the PATH in your environment?

[rhdtl78]

I confirm that by default the plugin uses the npm command available in the PATH and it is how I use it. The integration tests ensure that we do use the globally or locally installed node and npm commands according to the configuration and they run on both Windows, macOS and Linux. You are probably in a really specific case.

You will probably think that my question is stupid but I ask it anyway: is npm available in the PATH in your environment?

Sorry for late reply.

I'm using node installed by nvm.
I can us node globally, and nvm node path is also exported.

[bsautel]

Ok for node, but is npm also available in the PATH. If you run it in the same environment (terminal) directly or via Gradle, it should work. Are you sure you are using the same environment when running Gradle?

[rhdtl78]

Yeah. I'm sure it is same env. Maybe it caused by architecture. I can build project by Gradle with this plugin on Rosetta2, but not in M1 Native.

Maybe this issue related with this

[bsautel]

Indeed I did not noticed you are running a Mac M1. But I don't see why the npm command works when you run it from the terminal and not when it is launched by Gradle.

Can someone using a Mac M1 confirm that it the problem comes from the platform?

The issue #154 is not exactly the same problem. You are not asking the plugin to download and install Node.js, and this is what was reported as broken on Mac M1.

[rhdtl78]

Sorry for late replay.

Out of curiosity, if you run this with a x64 JVM does it work?

Yeah. I can run on x86 JVM OpenJDK 11 with rosetta2.
Maybe this is the workaround for now. You can close this issue.

[bsautel]

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?

[rhdtl78]

exactly.

[bsautel]

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 is more probable that it comes from an issue in the arm64 JVM.

Can you run this class using the x64 JVM and the arm one?

import java.io.IOException;

import static java.nio.charset.StandardCharsets.UTF_8;

public class JavaNpmExec {
    public static void main(String[] args) throws IOException {
        String command = "npm -version";
        Process child = Runtime.getRuntime().exec(command);
        System.out.println(new String(child.getInputStream().readAllBytes(), UTF_8));
        System.err.println(new String(child.getErrorStream().readAllBytes(), UTF_8));
    }
}

If you use Java 11+, you can simply create a JavaNpmExec.java file containing this anywhere on your filesystem and run it without compiling it by using java JavaNpmExec.java.

It runs npm which is expected to be available in the PATH (add it if it is not). It should work with the x64 JVM and probably not with the arm one.

[alexpartsch]

@bsautel I'm running into the same issue when having download = false set on a Apple M1 Book, running the given Java program with aarch64 on JDK 16:

/tmp % java JavaNpmExec.java
7.6.0

Using a x86 compatible JDK 16 on M1 yields the same:

/tmp % java /tmp/JavaNpmExec.java
7.6.0

[bsautel]

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 such big bug in the arm64 JVM!

We still have to find where does the issue come from. Let's check something on the Gradle side.

Gradle 7.0-rc1 was released a few days ago and adds full support of arm64 JVM. They don't talk about exec related issues in the release notes but could someone check whether the issue is still here when using an arm64 JVM with Gradle 7.0-rc1 please?

[michal-kaciuba]

Hi! Got the same issue on M1. Using Gradle v7.2 and gradle-node-plugin v3.2.1.

[deepy]

@MKaciuba just to confirm, that's getting Cannot run program "npm" (in directory ... when running with download = false right?

[lonely-lockley]

Faced this issue on Intel Mac. The funny thing that it stopped working without any external changes. The day before I've launched several builds successfully and today 'Cannot run program "npm"'. Everything works fine from terminal.
Liberica JDK 21, Gradle 8.5, Ventura 13.2.1, plugin version 7.0.1