Skip to content

Conversation

@lucacasonato
Copy link
Contributor

This changes esbuild.stop() to only resolve the returned promise when the child process has actually exited.

This is useful for when you have some resource sanitization in place that checks that the child process has actually been closed.

This changes `esbuild.stop()` to only resolve the returned promise when the child process has actually exited.

This is useful for when you have some resource sanitization in place that checks that the child process has actually been closed.
@nicolo-ribaudo
Copy link

nicolo-ribaudo commented Apr 28, 2025

Ping? :)

I just spent a while trying to figure out what was keeping my process alive longer than expected, and I noticed that ESBuild's process is still alive even after that the promise returned by esbuild.stop() resolves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants