ScriptLauncher fails to execute .exe with Node stream error. #7
Description
When attempting to run a Windows .exe (specifically a wrapped batch/utility executable) via ScriptLauncher, execution fails immediately with a Node.js stream error. The executable itself runs correctly when launched manually from Command Prompt.
NOTE: "Windows | Open File or Folder" works correctly, but "Windows | Run Script File" and "Windows | Launch Application" do not launch the specified file and do not send arguments.
Error Message
Error from ScriptLauncher: runScript:
The "chunk" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
Environment
OS: Windows 10 / Windows 11
ScriptLauncher: (1.8.0)
Executable Type: Windows .exe (compiled wrapper around a batch script)
Steps to Reproduce
Create or use a Windows .exe that accepts command-line arguments (e.g. %1) .
Configure ScriptLauncher to execute the .exe.
Trigger the script with/without explicitly passing an argument.
Observe immediate failure.
Expected Behavior
ScriptLauncher should:
Either execute the .exe
Actual Behavior
ScriptLauncher throws a Node.js error indicating an invalid stream chunk (undefined) and aborts execution.
The executable never runs.