quinoa's "npm run build" fails?

[kenyee]

Moved to a new machine and I get this error during a build on a project with quinoa that used to work:

* What went wrong:
Execution failed for task ':quarkusBuild'.
> io.quarkus.builder.BuildException: Build failure: Build failed due to errors
        [error]: Build step io.quarkiverse.quinoa.deployment.QuinoaProcessor#processBuild threw an exception: java.lang.RuntimeException: Error in Quinoa while running package manager build command: npm run build
        at io.quarkiverse.quinoa.deployment.PackageManager.build(PackageManager.java:60)
        at io.quarkiverse.quinoa.deployment.QuinoaProcessor.processBuild(QuinoaProcessor.java:126)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:925)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)

Would be nice if it included the output of npm, but has anyone ever hit this issue?

[kenyee]

ahh..running "npm run build" in the src/main/webui folder showed the real error:

npm run build

> webui@0.1.0 build
> react-scripts build

/var/folders/3x/2b22lrdx3fzdcxpf9nx6cm6c0000gp/T/build658723.sh: line 2: react-scripts: command not found

and doing "npm install react-scripts" fixes this error and allows quarkus to build.

[rmanibus]

I am facing the same issue. I still think that it would be valuable to display the npm log output.
Could one of the maintainer confirm if this is already possible or if this should be contributed ?