@palbase/backend 25.1.0 → 27.1.0

package/dist/module-Dl1KFVtc.d.cts

@@ -0,0 +1,54 @@
+/**
+ * A class the container can resolve, named by its own constructor.
+ *
+ * There is NO separate token concept — no strings, no symbols, no `@Inject`.
+ * An abstraction is an `abstract class`, which is still a runtime value and so
+ * is still a token. `never[]` on the parameters makes a token something you can
+ * NAME but not call: `Token` is an identity, not a factory.
+ */
+type Token<T = unknown> = abstract new (...args: never[]) => T;
+/**
+ * The four lists a module declares.
+ *
+ * `providers` is OWNERSHIP — a class belongs to exactly one module and this is
+ * where that is said. `exports` is VISIBILITY — what other modules may reach.
+ * `imports` is PERMISSION — whose exports this module may reach. `controllers`
+ * are the entry points the module owns.
+ *
+ * Position in a list means nothing; ownership is read from this declaration and
+ * from nowhere else — not from a directory, not from a file name, not from the
+ * class's own decorator (spec FR-009).
+ */
+interface ModuleDef {
+    imports?: Token[];
+    controllers?: Token[];
+    providers?: Token[];
+    exports?: Token[];
+}
+/** One `@Module` declaration: the class that carried it, and what it declared. */
+interface ModuleEntry {
+    mod: Token;
+    def: ModuleDef;
+}
+/**
+ * Declares a module.
+ *
+ * There is no root module and nothing to mount it into: registration IS the
+ * decorator running, which happens when the file is imported. A project with no
+ * module file at all is not an error — it simply owns nothing, and every entry
+ * point it declares is refused by name (FR-035) rather than quietly served.
+ */
+declare function Module(def: ModuleDef): ClassDecorator;
+/**
+ * TAKES the accumulated declarations — it does not read them.
+ *
+ * Same reason `__runStartHooks` splices (runtime.ts:297): a candidate bundle is
+ * imported into the SAME process as the live app it might replace. Reading
+ * would let the candidate build a container out of the live app's modules, and
+ * a discarded candidate would leave its own behind for the next release to
+ * adopt. Claiming makes each `createApp` see exactly the modules imported since
+ * the last one, and a rollback leave nothing behind.
+ */
+declare function __claimModules(): ModuleEntry[];
+
+export { Module as M, type Token as T, __claimModules as _, type ModuleDef as a };

package/dist/module-Dl1KFVtc.d.ts

@@ -0,0 +1,54 @@
+/**
+ * A class the container can resolve, named by its own constructor.
+ *
+ * There is NO separate token concept — no strings, no symbols, no `@Inject`.
+ * An abstraction is an `abstract class`, which is still a runtime value and so
+ * is still a token. `never[]` on the parameters makes a token something you can
+ * NAME but not call: `Token` is an identity, not a factory.
+ */
+type Token<T = unknown> = abstract new (...args: never[]) => T;
+/**
+ * The four lists a module declares.
+ *
+ * `providers` is OWNERSHIP — a class belongs to exactly one module and this is
+ * where that is said. `exports` is VISIBILITY — what other modules may reach.
+ * `imports` is PERMISSION — whose exports this module may reach. `controllers`
+ * are the entry points the module owns.
+ *
+ * Position in a list means nothing; ownership is read from this declaration and
+ * from nowhere else — not from a directory, not from a file name, not from the
+ * class's own decorator (spec FR-009).
+ */
+interface ModuleDef {
+    imports?: Token[];
+    controllers?: Token[];
+    providers?: Token[];
+    exports?: Token[];
+}
+/** One `@Module` declaration: the class that carried it, and what it declared. */
+interface ModuleEntry {
+    mod: Token;
+    def: ModuleDef;
+}
+/**
+ * Declares a module.
+ *
+ * There is no root module and nothing to mount it into: registration IS the
+ * decorator running, which happens when the file is imported. A project with no
+ * module file at all is not an error — it simply owns nothing, and every entry
+ * point it declares is refused by name (FR-035) rather than quietly served.
+ */
+declare function Module(def: ModuleDef): ClassDecorator;
+/**
+ * TAKES the accumulated declarations — it does not read them.
+ *
+ * Same reason `__runStartHooks` splices (runtime.ts:297): a candidate bundle is
+ * imported into the SAME process as the live app it might replace. Reading
+ * would let the candidate build a container out of the live app's modules, and
+ * a discarded candidate would leave its own behind for the next release to
+ * adopt. Claiming makes each `createApp` see exactly the modules imported since
+ * the last one, and a rollback leave nothing behind.
+ */
+declare function __claimModules(): ModuleEntry[];
+
+export { Module as M, type Token as T, __claimModules as _, type ModuleDef as a };