fix: use spawn's shell option to follow npm and fix batch script shells #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
A PR earlier today (#42) attempted to fix
spawn EINVAL
errors on Windows, but accidentally changed how arguments were passed to the custom shell. Thankfully a test in the pnpm repo caught this and failed.Changes
Instead of option 3, let's go with option 2.
Testing
I used
pnpm patch
to edit@pnpm/npm-lifecycle
to trigger a CI job in the pnpm repo. Running on my fork to make sure the fix above works.https://github.com/gluxon/pnpm/actions/runs/8692862152