@napi-rs/cli 3.10.0 → 3.10.2

package/docs/wasi.md

@@ -336,6 +336,23 @@ Consumers that need deterministic cleanup before process exit should use the
 deferred loader and call its `dispose()` function, or the `dispose` returned by
 `createInstance()`.
 
+Every termination goes through the emnapi thread manager
+(`PThread.terminateWorker`) rather than a bare `worker.terminate()`. The manager
+counts a worker exit as expected only for terminations it performed itself and
+reports any other one as a worker failure — a throw that lands inside Node.js's
+`exit` emit and strands the promise the termination depends on. The manager is
+captured while the emnapi module is being created, before the wasm is loaded, so
+it is reachable even from the initialization rollback — the one path where
+instantiation never returned.
+
+Disposal holds the event loop open with a timer of its own until the
+terminations settle, so `await dispose()` resolves even as the last statement of
+a script. The pool workers cannot do that themselves: they are unreferenced so
+an idle binding never keeps a process alive, and emnapi unreferences them again
+whenever one reports that its thread is ready. The timer is released the moment
+the terminations settle, and a binding that is never disposed still does not
+hold an idle process open.
+
 When type generation is disabled, the generated browser root exposes the
 binding as its default export. `napi new` also removes the template's
 `index.d.ts` and declaration metadata instead of publishing stale template

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@napi-rs/cli",
-  "version": "3.10.0",
+  "version": "3.10.2",
   "description": "Cli tools for napi-rs",
   "author": "LongYinan <lynweklm@gmail.com>",
   "homepage": "https://napi.rs/",