fix(workspaces): Use shell option on Windows in execa call
#11108
+110
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ands Add preferLocal and shell options to execa calls to properly resolve package manager executables on Windows, especially when Bun is installed via the bash installer. This fixes issue #11035 where "no package.json found" error occurs during create-turbo on Windows with Bun. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
anthonyshew
changed the title
shell option on Windows for package manager
anthonyshew
changed the title
shell option on Windows for package managershell option on Windows in execa call
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Addresses #11035 by adding
preferLocalandshelloptions toexecacalls for package manager commands. This resolves the "no package.json found" error that occurs when using Bun installed via bash installer on Windows.When Bun is installed via
curl -fsSL https://bun.sh/install | bash, it's placed in a Unix-style PATH that Node.js can't access without shell context. Usingshell: trueon Windows allows the shell to resolve these commands properly.Test Results
CI and canarying to be verified on Windows.