You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't dug deeply into the specifics of this issue since I'm replacing the library, and I'm pretty confident this project is no longer maintained, but I want to leave some information here.
The stream itself gets processed and upon completion results in the equivalent of process.exit(0), it will not continue even wrapped in try {} finally {} and will exit with status 0. The only way to capture the process before exiting seem to be by listening to beforeExit or exit on process.
If I swap the order so the progress stream is before the async generator, execution completes normally:
I haven't dug deeply into the specifics of this issue since I'm replacing the library, and I'm pretty confident this project is no longer maintained, but I want to leave some information here.
Effectively in node 16 I have:
The stream itself gets processed and upon completion results in the equivalent of
process.exit(0)
, it will not continue even wrapped intry {} finally {}
and will exit with status 0. The only way to capture the process before exiting seem to be by listening tobeforeExit
orexit
onprocess
.If I swap the order so the progress stream is before the async generator, execution completes normally:
I suspect it's related to this:
The text was updated successfully, but these errors were encountered: