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
Stdio is not inherited anymore in Lerna 5 #3214
Labels
Comments
I think the latest PR #3262 will fix your issue |
Thanks so much for the reproduction @BenoitZugmeyer! #3262 won't fix this issue, as that only dealt with an issue I had observed on |
BenoitZugmeyer
added a commit
to DataDog/browser-sdk
that referenced
this issue
Jul 27, 2022
In particular, lerna v5.3 is fixing an issue I have when doing a `yarn release`: lerna/lerna#3214
4 tasks
BenoitZugmeyer
added a commit
to DataDog/browser-sdk
that referenced
this issue
Jul 27, 2022
In particular, lerna v5.3 is fixing an issue I have when doing a `yarn release`: lerna/lerna#3214
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
I am using a
version
npm script to open an editor and let the developer check and edit the CHANGELOG before a release. With Lerna 4, it worked flawlessly. Starting with 5.0.0, Lerna captures the standard input and output when running a npm lifecycle, so terminal editors like Vim don't show up anymore.Expected Behavior
Restore the Lerna 4 behavior. When running a npm lifecycle, stdio should be inherited so the script can be interactive.
Steps to Reproduce
Minimal example to reproduce: lerna/repro#4
Then the script is stuck, vim does not show up.
Notes
If you run the same steps but install Lerna 4 instead, it works as expected.
Changing
pipe
toinherit
here fixes the issue.Failure Logs / Configuration
lerna.json
Nothing special:
Environment
The text was updated successfully, but these errors were encountered: