Cannot run an npx command in an exec node after upgrading from addon v15 to v17

[RomainGx]

Problem/Motivation

Hello, I got a flow that contains an exec node which runs an npx command. It ran well using add-node-red version 15. But I recently upgraded to version 17 and now I get an error:

• Without double quotes around the command (that's what I had before the update), the command runs indefinitely
• With double quotes around the command it fails fast:

{
    code: 127,
    message: Command failed: "npx tydom-client some other params"
/bin/bash: line 1: npx tydom-client some other params: No such file or directory
}

Example of npx command: npx tydom-client some other params

Expected behavior

The exec node should run an npx command without error.

Please also note that it works correctly when running a standalone NodeRed instance using npx instead of nom run. Npx does not work either with nodered-addon

Actual behavior

The exec node runs my npx command indefinitely.

Steps to reproduce

• Add an exec node with command npx cowsay hello (exec mode, not spawn)
• Run it: it will never stop until you kill it

[RomainGx]

Edited:

• I have tried running npx instead of nom run: it does not work either
• I installed a standalone NodeRed instance and npx works well

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[RomainGx]

The problem remains unsolved

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[RomainGx]

The problem remains. I abandonned the addon and installed a standalone node-red instance in another VM