gemi 0.115.0 → 0.117.0

package/dist/{chunk-n672d4g8.js → chunk-n9jyjp4a.js}

@@ -1,5 +1,5 @@
 // @bun
 class B{app;constructor(z){this.app=z}register(){}boot(){}shutdown(z){}}
-export{B as Lc};
+export{B as Nc};
 
-//# debugId=19EDA806C63FE2D764756E2164756E21
+//# debugId=83E3F05E08E87BD164756E2164756E21

package/dist/{chunk-n672d4g8.js.map → chunk-n9jyjp4a.js.map}

@@ -5,6 +5,6 @@
     "import type { Application } from \"../foundation/Application\";\n\n/**\n * What a provider's `shutdown()` may resolve: nothing, or whether it\n * abandoned work at the deadline. See `ServiceProvider` below.\n */\nexport type ProviderShutdownResult = void | { abandoned: boolean };\n\n/**\n * Every hook defaults to a no-op. `register()` binds services into the\n * container and must not resolve any of them; `boot()` runs after every\n * provider has registered, so it may resolve freely.\n *\n * `shutdown()` runs once when a production server is told to stop (`SIGTERM`\n * or `SIGINT`), after it has stopped accepting requests and the in-flight ones\n * have finished or run out of grace — so nothing a request needs is torn down\n * under it. Providers shut down in reverse registration order, so one\n * registered after another may still use it. Each is awaited, but under a\n * shared deadline (`GEMI_SHUTDOWN_PROVIDER_TIMEOUT`): one that overruns is\n * abandoned and the next begins, and one that throws is logged and does not\n * stop the rest. See `Application.shutdown`.\n *\n * Under `gemi dev` it also runs on every `bun --hot` reload, for the\n * application the reload replaced, once the new one is serving and the old\n * one's requests have finished (see `server/devReload.ts`). A hook that closes\n * something kept on `globalThis` across reloads would close it for the new\n * application too.\n *\n * `timeoutMs` is what is left of that shared deadline when this provider is\n * reached. A provider that waits for something — jobs finishing, a queue\n * draining — should bound its own wait by a little less than this, so that it\n * is still the one to report what it gave up on. Ignoring it is fine; the\n * provider is then simply abandoned at the deadline, with only a generic line\n * from `Application` to say so.\n *\n * A provider that bounds its own wait and gives up on work it was waiting for\n * resolves `{ abandoned: true }`. `Application` then reports it in `timedOut`\n * as if it had overrun, and the process exits `1` — the work was cut off just\n * the same, and an orchestrator or a log alert has to be able to see that from\n * the exit code. The provider names what it abandoned in its own log line.\n */\nexport abstract class ServiceProvider {\n  constructor(protected app: Application) {}\n\n  register(): void {}\n\n  boot(): void | Promise<void> {}\n\n  shutdown(options?: {\n    timeoutMs: number;\n  }): ProviderShutdownResult | Promise<ProviderShutdownResult> {}\n}\n"
   ],
   "mappings": ";AAyCO,MAAe,CAAgB,CACd,IAAtB,WAAW,CAAW,EAAkB,CAAlB,WAEtB,QAAQ,EAAS,EAEjB,IAAI,EAAyB,EAE7B,QAAQ,CAAC,EAEoD,EAC/D",
-  "debugId": "19EDA806C63FE2D764756E2164756E21",
+  "debugId": "83E3F05E08E87BD164756E2164756E21",
   "names": []
 }