nucleus-core-ts 0.9.600 → 0.9.701

package/dist/src/ElysiaPlugin/dbPoolConfig.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/src/ElysiaPlugin/routes/auth/admin/impersonate.d.ts

@@ -1,7 +1,12 @@
 import { Elysia } from 'elysia';
 import type { CreateSessionParams } from '../login';
 import type { AuthRouteConfig } from '../types';
-export declare function createImpersonateRoute(config: AuthRouteConfig, signAccessToken: (userId: string, roles?: string[], claims?: string[], tenant?: string) => string, signRefreshToken: (userId: string) => string, createSession: (params: CreateSessionParams) => Promise<string>, saveSessionToDb?: (sessionId: string, params: CreateSessionParams, schemaName?: string) => Promise<{
+export declare function createImpersonateRoute(config: AuthRouteConfig, signAccessToken: (userId: string, roles?: string[], claims?: string[], tenant?: string) => string, signRefreshToken: (userId: string) => string, verifyRefreshToken: (token: string) => {
+    valid: boolean;
+    payload?: {
+        sub: string;
+    };
+}, createSession: (params: CreateSessionParams) => Promise<string>, saveSessionToDb?: (sessionId: string, params: CreateSessionParams, schemaName?: string) => Promise<{
     requiresApproval?: boolean;
     sessionId?: string;
 } | undefined>, cookieConfig?: {

package/dist/src/ElysiaPlugin/routes/auth/oauth/index.d.ts

@@ -9,6 +9,26 @@ interface MagicLinkToken {
     tokenHash: string;
     expiresAt: Date;
 }
+/**
+ * Build the Set-Cookie for the short-lived, single-use OAuth `state` CSRF cookie.
+ *
+ * Path is ALWAYS `/`, NOT the backend's internal OAuth `basePath`. The cookie is
+ * set when the browser starts the flow and must be re-sent on the provider's
+ * callback, but the EXTERNAL callback path is decided by the deployment's
+ * ingress/proxy (commonly `/api/auth/oauth/<provider>/callback` or
+ * `/oauth/<provider>`) and routinely differs from the backend-internal basePath
+ * (`/auth/oauth`). A basePath-scoped cookie then silently fails the browser's
+ * path match on the callback, the cookie is never attached, and the M6 CSRF
+ * check rejects the login with `invalid_state`. `Path=/` makes the cookie
+ * round-trip regardless of how the edge remaps the OAuth routes. `SameSite=Lax`
+ * is required so the top-level GET redirect back from the IdP still carries it;
+ * the cookie stays HttpOnly + single-use, so the wider path does not weaken CSRF.
+ */
+export declare function buildOAuthStateCookie(value: string, opts: {
+    maxAge: number;
+    secure?: boolean;
+    domain?: string;
+}): string;
 export declare function createOAuthRoutes(config: AuthRouteConfig, oauthService: OAuthService, signAccessToken: (userId: string, roles?: string[], claims?: string[], tenant?: string) => string, signRefreshToken: (userId: string) => string, createSession: (params: CreateSessionParams) => Promise<string>, saveSessionToDb?: (sessionId: string, params: CreateSessionParams, schemaName?: string) => Promise<{
     requiresApproval?: boolean;
     sessionId?: string;

package/dist/src/ElysiaPlugin/routes/auth/oauth/oauthStateCookie.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/src/ElysiaPlugin/utils.d.ts

@@ -16,6 +16,23 @@ export declare function signNewAccessToken({ sessionData, options, refreshTokenI
     /** H9: tenant schema to bind into the token (x-tenant-schema). */
     tenant?: string;
 }): string;
+/**
+ * Resolve the shared `pg` Pool options from `database.pool`, applying safe
+ * defaults. `max` bounds the total connections one instance holds (the guard
+ * against "53300 too many clients"); `idleTimeoutMillis` reaps idle clients;
+ * `connectionTimeoutMillis` fails fast under exhaustion instead of hanging.
+ */
+export declare function resolveDbPoolConfig(pool?: {
+    max?: number;
+    idleTimeoutMillis?: number;
+    connectionTimeoutMillis?: number;
+    maxUses?: number;
+}): {
+    max: number;
+    idleTimeoutMillis: number;
+    connectionTimeoutMillis: number;
+    maxUses?: number;
+};
 export declare function toAudit(payload: AuditPayload | null, summary: string, opts?: {
     /** Override the actor for this audit (e.g. the user behind a revoked/forged token). */
     userId?: string | null;

package/dist/src/types.d.ts

@@ -123,6 +123,21 @@ export interface NucleusConfigOptions {
     database: {
         url?: string;
         type?: 'postgres';
+        /**
+         * Connection-pool tuning for the single shared `pg` Pool. A multi-tenant
+         * deployment uses ONE pool for all tenant schemas (schema is switched per
+         * query), so `max` bounds the TOTAL connections one app instance holds —
+         * keep it well under Postgres `max_connections` divided by the number of
+         * instances to avoid "53300 too many clients". Idle connections are reaped
+         * after `idleTimeoutMillis`; acquiring a connection fails fast after
+         * `connectionTimeoutMillis` (surfacing exhaustion instead of hanging).
+         */
+        pool?: {
+            max?: number;
+            idleTimeoutMillis?: number;
+            connectionTimeoutMillis?: number;
+            maxUses?: number;
+        };
         isMultiTenant?: boolean;
         schemas?: string[];
         /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nucleus-core-ts",
-  "version": "0.9.600",
+  "version": "0.9.701",
   "description": "Production-ready, enterprise-grade TypeScript framework for building multi-tenant APIs",
   "author": "Hidayet Can \u00d6zcan <hidayetcan@gmail.com>",
   "license": "SEE LICENSE IN LICENSE",

package/schemas/config.nucleus.json

@@ -31,6 +31,27 @@
             "postgres"
           ]
         },
+        "pool": {
+          "type": "object",
+          "properties": {
+            "max": {
+              "type": "number"
+            },
+            "idleTimeoutMillis": {
+              "type": "number",
+              "description": "default 10"
+            },
+            "connectionTimeoutMillis": {
+              "type": "number",
+              "description": "default 30000"
+            },
+            "maxUses": {
+              "type": "number",
+              "description": "default 10000"
+            }
+          },
+          "description": "Connection-pool tuning for the single shared `pg` Pool. A multi-tenant deployment uses ONE pool for all tenant schemas (schema is switched per query), so `max` bounds the TOTAL connections one app instance holds — keep it well under Postgres `max_connections` divided by the number of instances to avoid \"53300 too many clients\". Idle connections are reaped after `idleTimeoutMillis`; acquiring a connection fails fast after `connectionTimeoutMillis` (surfacing exhaustion instead of hanging)."
+        },
         "isMultiTenant": {
           "type": "boolean"
         },