@lunora/auth 1.0.0-alpha.2 → 1.0.0-alpha.21

package/dist/packem_shared/create-auth.d-M36jwG_Y.d.mts

@@ -1,58 +0,0 @@
-import { betterAuth, BetterAuthOptions } from 'better-auth';
-/**
-* Lunora's options pass straight through to better-auth — the only thing we add
-* is requiring `secret` up front so a misconfigured deployment fails loudly
-* instead of at the first sign-in.
-*
-* For `database`, prefer `lunoraD1Adapter` (`database: lunoraD1Adapter(env.DB)`)
-* over passing the raw `env.DB`. better-auth *does* accept a D1Database directly,
-* but it then resolves its Kysely adapter via a runtime `await import(...)` inside
-* `auth.$context` — and that import never settles under `@cloudflare/vite-plugin`'s
-* worker runner, hanging every auth request in `pnpm dev`. The explicit adapter
-* skips it, so dev and prod behave the same. (Raw `env.DB` is still correct for
-* the migration-only instance — see `lunoraD1Adapter`'s note.)
-*
-* Session rotation / richer session policies are configured via the `session`
-* field (a `SessionPolicy`); Lunora validates it for obviously-broken
-* durations and forwards it verbatim to better-auth. See `sessionPresets`
-* for ready-made rotation/expiry trade-offs.
-*
-* ## Serverless background tasks (Cloudflare Workers)
-*
-* better-auth runs some work *after* sending the response — most importantly the
-* password-reset email, whose background send is what keeps reset responses
-* constant-time (a timing-attack defence: the response doesn't reveal whether
-* the account exists). On Cloudflare Workers a promise that isn't handed to
-* `ctx.waitUntil` can be cancelled the moment the response returns, dropping
-* that send and weakening the guarantee. Wire your request's `ctx.waitUntil`
-* into better-auth's background handler so the work survives:
-*
-* ```ts
-* // in your worker fetch handler, where `ctx: ExecutionContext` is in scope
-* const auth = createAuth({
-*     secret: env.AUTH_SECRET,
-*     database: lunoraD1Adapter(env.DB),
-*     advanced: {
-*         backgroundTasks: { handler: (promise) => ctx.waitUntil(promise) },
-*     },
-* });
-* ```
-*
-* (Lunora can't set this for you — `ctx.waitUntil` is per-request, but
-* `createAuth` runs once at worker setup.)
-*/
-type LunoraAuthOptions = BetterAuthOptions;
-/**
-* The full better-auth instance: `auth.handler` accepts a `Request` and
-* returns a `Response` (used by `handleAuthRequest`); `auth.api`
-* exposes the typed endpoint surface for server-side calls (e.g.
-* `auth.api.getSession({ headers })` inside a query/mutation).
-*/
-type LunoraAuth = ReturnType<typeof betterAuth>;
-/**
-* Create the auth instance. Thin wrapper around `betterAuth` that enforces
-* the `secret` requirement at construction time so misconfigured deployments
-* fail loudly at the first fetch rather than the first sign-in attempt.
-*/
-declare const createAuth: (options: LunoraAuthOptions) => LunoraAuth;
-export { LunoraAuth as L, LunoraAuthOptions as a, createAuth as c };

package/dist/packem_shared/create-auth.d-M36jwG_Y.d.ts

@@ -1,58 +0,0 @@
-import { betterAuth, BetterAuthOptions } from 'better-auth';
-/**
-* Lunora's options pass straight through to better-auth — the only thing we add
-* is requiring `secret` up front so a misconfigured deployment fails loudly
-* instead of at the first sign-in.
-*
-* For `database`, prefer `lunoraD1Adapter` (`database: lunoraD1Adapter(env.DB)`)
-* over passing the raw `env.DB`. better-auth *does* accept a D1Database directly,
-* but it then resolves its Kysely adapter via a runtime `await import(...)` inside
-* `auth.$context` — and that import never settles under `@cloudflare/vite-plugin`'s
-* worker runner, hanging every auth request in `pnpm dev`. The explicit adapter
-* skips it, so dev and prod behave the same. (Raw `env.DB` is still correct for
-* the migration-only instance — see `lunoraD1Adapter`'s note.)
-*
-* Session rotation / richer session policies are configured via the `session`
-* field (a `SessionPolicy`); Lunora validates it for obviously-broken
-* durations and forwards it verbatim to better-auth. See `sessionPresets`
-* for ready-made rotation/expiry trade-offs.
-*
-* ## Serverless background tasks (Cloudflare Workers)
-*
-* better-auth runs some work *after* sending the response — most importantly the
-* password-reset email, whose background send is what keeps reset responses
-* constant-time (a timing-attack defence: the response doesn't reveal whether
-* the account exists). On Cloudflare Workers a promise that isn't handed to
-* `ctx.waitUntil` can be cancelled the moment the response returns, dropping
-* that send and weakening the guarantee. Wire your request's `ctx.waitUntil`
-* into better-auth's background handler so the work survives:
-*
-* ```ts
-* // in your worker fetch handler, where `ctx: ExecutionContext` is in scope
-* const auth = createAuth({
-*     secret: env.AUTH_SECRET,
-*     database: lunoraD1Adapter(env.DB),
-*     advanced: {
-*         backgroundTasks: { handler: (promise) => ctx.waitUntil(promise) },
-*     },
-* });
-* ```
-*
-* (Lunora can't set this for you — `ctx.waitUntil` is per-request, but
-* `createAuth` runs once at worker setup.)
-*/
-type LunoraAuthOptions = BetterAuthOptions;
-/**
-* The full better-auth instance: `auth.handler` accepts a `Request` and
-* returns a `Response` (used by `handleAuthRequest`); `auth.api`
-* exposes the typed endpoint surface for server-side calls (e.g.
-* `auth.api.getSession({ headers })` inside a query/mutation).
-*/
-type LunoraAuth = ReturnType<typeof betterAuth>;
-/**
-* Create the auth instance. Thin wrapper around `betterAuth` that enforces
-* the `secret` requirement at construction time so misconfigured deployments
-* fail loudly at the first fetch rather than the first sign-in attempt.
-*/
-declare const createAuth: (options: LunoraAuthOptions) => LunoraAuth;
-export { LunoraAuth as L, LunoraAuthOptions as a, createAuth as c };