Spuriously escapes some characters on windows

[msakrejda]

I'm working with node-foreman in Powershell and noticed that it seems to escape some characters in the command arguments before invoking the command. Here are some simple steps to reproduce:

> cat .\test.js
console.log(...process.argv.slice(2))
> npx node .\test.js hello:world
hello:world
> npx nf run node .\test.js hello:world
[WARN] No ENV file found
hello\:world

The backslash breaks some tools like knex which have subcommands that include a colon. I'm not sure why this is happening, but pretty sure based on the above that it's node-foreman causing that backslash to be inserted. Any ideas?

Windows 10, foreman 3.0.1

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.