Quinoa cannot use already installed node version

[nimo23]

I have node (with npm) installed on my machine:

~ » node -v                                                   
v23.1.0

~ » npm -v                                                     
10.9.0

and a correct package.json with package-lock.json in my src/main/webui-folder of my quarkus-project.

However, when starting Quarkus Dev with Quinoa I get the following error:

Caused by: java.lang.RuntimeException: Error in Quinoa while running package manager install command: npm install
	at io.quarkiverse.quinoa.deployment.packagemanager.PackageManagerRunner.install(PackageManagerRunner.java:84)
	at io.quarkiverse.quinoa.deployment.QuinoaProcessor.install(QuinoaProcessor.java:147)
	at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)

So it seems that Quinoa cannot use the Node version that is already installed globally, or?

Therefore I need to allow Quinoa to install it manually:

# Quinoa
quarkus.quinoa.package-manager-install=true
quarkus.quinoa.package-manager-install.node-version=23.1.0

Is there a way to allow Quinoa to use the globally installed node version or is this considered a bad practice?

[ia3andy]

It should work, is it in your PATH env when running Quarkus?

[nimo23]

It should work, is it in your PATH env when running Quarkus?

I'm using Mac OS with zsh and when I type node -v in my terminal it prints the version:

~ » node -v                                                   
v23.1.0

~ » npm -v                                                     
10.9.0

However, where and how do I put PATH env?

[ia3andy]

echo $PATH

[ia3andy]

I just tried a code quarkus app with Quinoa and Rest (and removed the node install from properties) and it works:

1-06 11:09:10,762 INFO  [io.qua.qui.dep.fra.FrameworkType] (build-28) Quinoa detected 'VITE' frameworkType from package.json file.
2024-11-06 11:09:10,967 INFO  [io.qua.qui.dep.QuinoaProcessor] (build-16) Quinoa didn't detect a node_modules directory, let's install packages...
2024-11-06 11:09:10,968 INFO  [io.qua.qui.dep.pac.PackageManagerRunner] (build-16) Running Quinoa package manager install command: npm install
2024-11-06 11:09:12,465 INFO  [io.qua.qui.dep.pac.PackageManagerRunner] (build-29) Running Quinoa package manager live coding as a dev service: npm run dev
2024-11-06 11:09:14,019 INFO  [io.qua.qui.dep.ForwardedDevProcessor] (build-29) Quinoa package manager live coding is up and running on port: 5173 (in 1554ms)
2024-11-06 11:09:14,023 INFO  [io.qua.qui.dep.ForwardedDevProcessor] (build-16) Quinoa is forwarding unhandled requests to port: 5173
__  ____  __  _____   ___  __ ____  ______
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/
2024-11-06 11:09:14,484 INFO  [io.quarkus] (Quarkus Main Thread) try-node 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.16.1) started in 4.147s. Listening on: http://localhost:8080

2024-11-06 11:09:14,485 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2024-11-06 11:09:14,485 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, quinoa, rest, smallrye-context-propagation, vertx]

[ia3andy]

~/D/try-node> node -v
v23.1.0
~/D/try-node> npm -v
10.9.0

[nimo23]

echo $PATH

Oh yes. The print of echo $PATH does not show any node version . Strange because typing node -v in my terminal (from any directory) prints the version in the terminal, so I assumed it was already in my path. But I use homebrew and zsh. I think the path is symbolically linked, but not in my Path . Adding it explicitly solves this problem.