-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Do not force quit Rollup or close stdout #5004
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you for your contribution! ❤️You can try out this pull request locally by installing Rollup via npm install rollup/rollup#no-force-quit or load it into the REPL: |
Codecov Report
@@ Coverage Diff @@
## master #5004 +/- ##
=======================================
Coverage 98.96% 98.97%
=======================================
Files 222 222
Lines 8155 8157 +2
Branches 2241 2243 +2
=======================================
+ Hits 8071 8073 +2
Misses 30 30
Partials 54 54
|
66c0976
to
67a287b
Compare
67a287b
to
ed1e93f
Compare
202a64d
to
b916a08
Compare
This PR has been released as part of rollup@3.22.1. You can test it via |
I will, thank you rollup-bot |
3.23.0 does not resolve vercel/turborepo#4983 |
reverts #4969, #4983
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
prepublishOnly
lifecycle #4998Description
This basically reverts #4969 and #4983 as calling
process.exit()
orprocess.stdout.end()
seems to break various workflows. Instead, we should find out what keeps Rollup from quitting in the first place, maybe some plugins?