lifecycleion 0.0.13 → 0.0.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- # Lifecycleion v0.0.13
1
+ # Lifecycleion v0.0.14
2
2
 
3
3
  [![npm version](https://badge.fury.io/js/lifecycleion.svg)](https://badge.fury.io/js/lifecycleion)
4
4
 
@@ -85,7 +85,7 @@ manager.registerComponent(new MyComponent('my-component'));
85
85
  await manager.startAllComponents();
86
86
  ```
87
87
 
88
- Tip: listen for `lifecycle-manager:shutdown-completed` when you want one place to react to shutdown results from manual stops, signals like `SIGINT` / `SIGTERM`, or logger-exit hooks. If `timedOut` is `true`, the payload reflects the result when the manager stopped waiting.
88
+ Tip: listen for `lifecycle-manager:shutdown-completed` when you want one place to react to shutdown results from manual stops, signals like `SIGINT` / `SIGTERM`, or logger-exit hooks. This is the centralized hook for logging or follow-up policy when `timedOut` is `true` or `stalledComponents` is non-empty. If `timedOut` is `true`, the payload reflects the result when the manager stopped waiting. Use repeated shutdown escalation separately when you want additional shutdown requests to retry or force behavior.
89
89
 
90
90
  ## Available Libraries
91
91