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
feat(exec): support shell interpreter #4328
feat(exec): support shell interpreter #4328
Conversation
Does it need to be configurable or should we just make it on by default? |
Run pnpm changeset in the root of the repository and describe your changes. The resulting files should be committed as they will be used during release. |
daebed5
to
ff53e94
Compare
Okey. Done. |
I wonder if Lerna uses the same solution. They claim that env variables work with exec: https://github.com/lerna/lerna/tree/main/commands/exec |
Yes, looks like they set it to true: |
OK, it makes sense to follow Yarn's approach. Does Yarn have a similar option as well? |
By default, pnpm behaves in the same way as yarn, but it would be better if we just provided a switch on top of this. |
Maybe in the future I can also provide a cli options for yarn and make yarn support |
Fixed: #4320
Once this PR has been merged, the following commands will be supported: