fix(core): add option for async logger compatibility #15986
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When using
enableShutdownHooks(), NestJS callsprocess.kill(process.pid, signal)after shutdown hooks complete. This does not properly trigger the Node.js'exit'event, which prevents async loggers like Pino (withpino.transport()) from flushing their buffered logs before the process terminates.Issue Number: #15978
What is the new behavior?
Added a new
useProcessExitoption toenableShutdownHooks()Does this PR introduce a breaking change?