We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when a command such as chokidar *.* --initial -c "echo ""Hello World!""" is executed on windows, the output is
chokidar *.* --initial -c "echo ""Hello World!"""
\"Hello World!\"
rather than the expected
"Hello World!"
This appears to be caused by some weird default behavior of childProcess.spawn when windowsVerbatimArguments is not set to true.
childProcess.spawn
windowsVerbatimArguments
true
The quick fix is to just add the option to utils.js
child = childProcess.spawn(SHELL_PATH, [EXECUTE_OPTION, cmd], { cwd: opts.cwd, stdio: opts.pipe ? 'inherit' : null, windowsVerbatimArguments: true });
however child_process.spawn now has a shell option that looks like it would simplify things here:
child_process.spawn
shell
child = childProcess.spawn(cmd, { cwd: opts.cwd, stdio: opts.pipe ? 'inherit' : null, shell: true })
The text was updated successfully, but these errors were encountered:
Yup, I was actually experimenting with this myself because otherwise tests do fail on Windows (with git bash). See kimmobrunfeldt/chokidar-cli@master...XhmikosR:test-win
Which would also fix #62.
But then I couldn't make tests pass without setting pipe: true in tests.
pipe: true
We need to add cross-platform CI testing for sure, and look into switching to shell ASAP.
Sorry, something went wrong.
$SHELL
Successfully merging a pull request may close this issue.
when a command such as
chokidar *.* --initial -c "echo ""Hello World!"""
is executed on windows, the output israther than the expected
This appears to be caused by some weird default behavior of
childProcess.spawn
whenwindowsVerbatimArguments
is not set totrue
.The quick fix is to just add the option to utils.js
however
child_process.spawn
now has ashell
option that looks like it would simplify things here:The text was updated successfully, but these errors were encountered: