-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
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
path.normalize(command) breaks local command on rebased cwd #90
Comments
Thanks for the report, I will look into this shortly. |
satazor
added a commit
that referenced
this issue
Jan 31, 2018
I'm sorry for this unfortunate bug. #91 fixes it and a release will follow soon. |
satazor
added a commit
that referenced
this issue
Jan 31, 2018
satazor
added a commit
that referenced
this issue
Jan 31, 2018
This actually fixes another bug with `options.cwd` on Windows. Closes #90.
satazor
added a commit
that referenced
this issue
Jan 31, 2018
This actually fixes another bug with `options.cwd` on Windows. Closes #90.
|
Spectacular, thank you! I will verify first thing tomorrow.
… On Jan 30, 2018, at 20:49, André Cruz ***@***.***> wrote:
v6.0.4 released, could you try it out and give feedback?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The recent ginormous v6 commit introduced an unconditional
path.normalize()
wrapping the command, which breaksspawn('./foo', { cwd: 'subdir' )
:node-cross-spawn/lib/parse.js
Line 107 in e77b8f2
I can't say what bug it was intended to fix, as the giant commit perverts all useful context. It is definitely breaking posix "local relative on rebased cwd" calls.
Reproduction
Async vs sync makes no difference, but the sync calls are easier to demonstrate.
subdir/foo
:test.js
:Upgrading cross-spawn to v6 in https://github.com/yargs/yargs current master with no other changes will demonstrate this "in the wild".
yargs test failure log
The text was updated successfully, but these errors were encountered: