EINVAL crash on latest nodejs

[TwitchBronBron]

There's a weird crash with the latest version of NodeJS when running ropm.

$ ropm install roku-requests
Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at Object.spawn (node:child_process:760:9)
    at C:\Users\bronley\AppData\Roaming\npm\node_modules\ropm\dist\util.js:24:40
    at new Promise (<anonymous>)
    at Util.spawnAsync (C:\Users\bronley\AppData\Roaming\npm\node_modules\ropm\dist\util.js:23:16)
    at Util.spawnNpmAsync (C:\Users\bronley\AppData\Roaming\npm\node_modules\ropm\dist\util.js:37:21)
    at InstallCommand.npmInstall (C:\Users\bronley\AppData\Roaming\npm\node_modules\ropm\dist\commands\InstallCommand.js:70:27)
    at async InstallCommand.run (C:\Users\bronley\AppData\Roaming\npm\node_modules\ropm\dist\commands\InstallCommand.js:39:13) {
  errno: -4071,
  code: 'EINVAL',
  syscall: 'spawn'
} 

[OLSA]

I get this error while trying to install ropm modules (my node version 20.18.1).
The error occurs because recent versions of Node.js block spawning .cmd files directly for security reasons (in this case npm.cmd). This can be resolved by adding { shell: true } to the options passed to child_process.spawn (link).

In my case, I directly edited the file node_modules\ropm\dist\util.js at line 24.
Originally was:

const child = childProcess.spawn( command, args !== null && args !== void 0 ? args : [], Object.assign( Object.assign({}, (options !== null && options !== void 0 ? options : {})), { stdio: 'inherit' } ) );

modified it to:

const child = childProcess.spawn( command, args !== null && args !== void 0 ? args : [], Object.assign( Object.assign({}, (options !== null && options !== void 0 ? options : {})), { stdio: 'inherit', shell: true } ) );

This change seems to resolve the issue, as the module installation now works correctly.
Regards.

[addison-adler]

I am also seeing this error. Has this fix been added to a published version of ropm?

I tried to use the line change mentioned above but it still didn't work for me 🙁

[addison-adler]

@OLSA Thank you for your insights! We applied the patch and it's released now in version 0.10.29