Fix nodejs/typescript probes when the Node interpreter is not in PATH

Change-Id: I9302a631450a43c25b5cf9bac6b5299f2b728683
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>

1 files changed, 8 insertions, 5 deletions

diff --git a/src/lib/corelib/api/runenvironment.cpp b/src/lib/corelib/api/runenvironment.cpp
index 4c4b4e681..c9095b708 100644
--- a/src/lib/corelib/api/runenvironment.cpp
+++ b/src/lib/corelib/api/runenvironment.cpp
@@ -280,11 +280,14 @@ int RunEnvironment::doRunTarget(const QString &targetBin, const QStringList &arg
     }
 
     if (completeSuffix == QLatin1String("js")) {
-        // The Node.js binary is called nodejs on Debian/Ubuntu-family operating systems due to a
-        // conflict with another package containing a binary named node
-        targetExecutable = findExecutable(QStringList()
-                                          << QLatin1String("nodejs")
-                                          << QLatin1String("node"));
+        targetExecutable = d->resolvedProduct->moduleProperties->moduleProperty(
+                    QLatin1String("nodejs"), QLatin1String("interpreterFilePath")).toString();
+        if (targetExecutable.isEmpty())
+            // The Node.js binary is called nodejs on Debian/Ubuntu-family operating systems due to
+            // conflict with another package containing a binary named node
+            targetExecutable = findExecutable(QStringList()
+                                              << QLatin1String("nodejs")
+                                              << QLatin1String("node"));
         targetArguments.prepend(targetBin);
     }