@dunx/auth 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,251 @@
+# @dunx/auth
+
+[Better Auth](https://better-auth.com) for dunx. **This package is not an
+authentication system** — better-auth is, and it is very good at it. This is the
+wiring: a module that builds the instance from your `ConfigService`, five routes that
+mount its handler, a guard that composes with the `@Public()` and `@Roles()` metadata
+`@dunx/http` already carries, and two adapters that let it drive Bun's own APIs.
+
+`better-auth` is a **required peer dependency**. Install it yourself and own its
+version — dunx does not bundle it — but it is not optional, because this package
+imports `betterAuth` as a value and cannot load without it. Marking it optional would
+trade an install-time warning for a module-resolution crash.
+
+```bash
+bun add @dunx/auth better-auth
+```
+
+`drizzle-orm` **is** an optional peer, needed only by `@dunx/auth/drizzle` — which is
+its own subpath precisely so that a Prisma, Kysely or MongoDB app never loads it.
+`dist/index.js` contains no reference to drizzle, which is the test a peer has to
+pass to be called optional.
+
+There is no dunx sign-in flow, no dunx session table, no dunx password reset and no
+dunx OAuth. Every one of those is a better-auth feature reached through
+`AuthModule.forRoot`'s options, which **are** better-auth's `BetterAuthOptions`. Its
+documentation is the documentation.
+
+## What dunx adds
+
+| Export                | What it is                                                            |
+| --------------------- | --------------------------------------------------------------------- |
+| `AuthModule`          | `forRoot` / `forRootAsync`, binding the instance and mounting it       |
+| `Auth`                | The injection token for the better-auth instance                      |
+| `SessionGuard`        | Middleware: authenticates, then reads `@Public()` and `@Roles()`       |
+| `AuthContext`         | The authenticated caller, reachable from any service in the request    |
+| `Principal`           | `{ session, user }` — better-auth's own inferred session type          |
+| `bunPassword`         | `Bun.password` bcrypt in place of better-auth's JavaScript scrypt      |
+| `redisStorage`        | `secondaryStorage` over `Bun.RedisClient`                             |
+| `drizzleDatabase`     | `database` over the drizzle handle `@dunx/infra/db` already opened     |
+| `rolesOf`             | The `admin` plugin's `role` column read as a list                     |
+| `AuthOptions`         | The resolved options, the `basePath` and where the handler mounted     |
+
+## Getting started
+
+```ts
+import { AuthModule } from '@dunx/auth';
+import { drizzleDatabase } from '@dunx/auth/drizzle';
+import { Module } from '@dunx/core';
+import { DbConnection } from '@dunx/infra/db';
+import { admin, bearer } from 'better-auth/plugins';
+
+@Module({
+  imports: [
+    AuthModule.forRootAsync({
+      useFactory: (config: AppConfigService, connection: DbConnection) => ({
+        secret: config.get('auth').secret,
+        baseURL: config.get('appUrl'),
+        database: drizzleDatabase(connection),
+        emailAndPassword: { enabled: true },
+        plugins: [admin(), bearer()],
+      }),
+      inject: [AppConfigService, DbConnection] as const,
+    }),
+  ],
+})
+export class AccountsModule {}
+```
+
+That is the whole integration. `forRoot(options)` is the same thing without a factory,
+for when the secret is not behind config.
+
+`forRootAsync` exists for the one reason it exists on `LoggerModule`, `DbModule` and
+the rest: a zero-argument function cannot read `ConfigService`. It is not a second
+mechanism — dunx settles every async factory before the first constructor runs, so
+the instance is built and the connection handshaked before anything can ask for
+either.
+
+### The database tables
+
+**dunx ships no schema for better-auth's tables.** They are better-auth's, they change
+with the plugins you enable, and its own CLI generates them:
+
+```bash
+bunx @better-auth/cli generate
+```
+
+Put the result in the schema object you already hand `@dunx/infra/db`, and
+`drizzleDatabase(connection)` needs no schema argument — `@dunx/infra/db` builds its
+handle with `drizzle({ client, schema })`, and better-auth's adapter reads
+`db._.fullSchema` off it. `examples/full/src/database/auth.schema.ts` is a
+generated schema in place.
+
+A framework carrying its own copy of a library's tables is a copy that rots against
+the library that reads them.
+
+## Mounting
+
+`AuthHandler` puts better-auth's `(request: Request) => Promise<Response>` behind five
+wildcard routes — `GET`, `POST`, `PUT`, `PATCH` and `DELETE` at `<basePath>/*`.
+`Bun.serve` matches a wildcard natively, so **Bun is still the router**: dunx does not
+restate, wrap or re-dispatch a single better-auth endpoint, and the `Response` comes
+back untouched, `Set-Cookie` headers and redirects included.
+
+`basePath` is better-auth's own option, defaulting to `/api/auth`.
+
+### With `setGlobalPrefix`
+
+better-auth resolves an endpoint by comparing the **whole pathname** to its
+`basePath`, so a global prefix makes the mount and the base path two different
+strings for one URL:
+
+```ts
+// app.setGlobalPrefix('api') turns the `/auth` route into `/api/auth`.
+AuthModule.forRootAsync({ useFactory: () => ({ basePath: '/api/auth', ... }) }, '/auth');
+```
+
+The second argument is the **route** path; `basePath` is what the browser sees. Get it
+wrong and the first request through the handler fails with an `AuthError` naming both
+paths, rather than better-auth quietly answering 404 to everything.
+
+## The guard
+
+```ts
+// Global — every route needs a session unless it says otherwise.
+HttpFactory.create(root, { middleware: [SessionGuard] });
+
+// or scoped — this controller needs one, nothing else does.
+@UseGuards(SessionGuard)
+@Controller('profile')
+class ProfileController {}
+```
+
+`AuthModule` registers `SessionGuard` as a provider either way. It resolves the
+session through better-auth's own `api.getSession`, so a cookie and the `bearer`
+plugin's `Authorization: Bearer <token>` both work, and then reads the metadata
+`@dunx/http` already had:
+
+- **`@Public()`** — skipped outright. No session lookup, no rejection, no role check.
+  That is what makes the guard safe to install globally: `AuthHandler` is `@Public()`,
+  and a sign-in endpoint that required a session could never be reached.
+- **`@Roles('admin', 'editor')`** — a 403 unless the caller holds one of them.
+  `@dunx/openapi` already reads the same key for its security schemes.
+
+A public route that wants to *adapt* to an optional caller asks better-auth itself:
+
+```ts
+const principal = await this.auth.api.getSession({ headers: req.headers });
+```
+
+One line, and it keeps a session lookup off every public request in the app.
+
+## Reaching the caller
+
+`AuthContext` is `AsyncLocalStorage`, so a service three constructor hops from the
+route sees the principal without it being threaded through a signature:
+
+```ts
+export class Audit {
+  constructor(private readonly auth: AuthContext) {}
+
+  entries(): readonly string[] {
+    const { user } = this.auth.require(); // 401 if there is none
+    return this.log.forUser(user.id);
+  }
+}
+```
+
+`current()` returns `Principal | undefined`; `require()` throws a 401.
+
+Two alternatives were rejected. Request-scoped DI was measured and turned down
+(`docs/ARCHITECTURE.md`), and hanging the principal off `req` reaches a route handler
+but nothing a route handler calls. `AsyncLocalStorage` is a Node built-in Bun
+implements natively, and it is already how `@dunx/core` carries request state.
+
+It is a **second** store rather than a key in `RequestContext`, because that one is
+the log record — every field in it is serialized into every line the request writes,
+so a session object there would be noise on each entry and a redaction hazard in the
+ones that matter. What does go there is `userId`, which is why every log line inside a
+guarded request is already correlated to the user.
+
+### Plugin types
+
+`Auth` is generic over the options it was built from, the same trick
+`@dunx/infra/db` uses for drizzle's schema: the token is the erased class, the type
+argument rides on the annotation.
+
+```ts
+export const authOptions = { plugins: [admin()], ... } as const;
+
+// `api` here has the admin plugin's endpoints on it.
+constructor(private readonly auth: Auth<typeof authOptions>) {}
+```
+
+Written bare, `Auth` carries better-auth's core endpoints only.
+
+## Password hashing
+
+better-auth's default hasher is **pure-JavaScript scrypt**. `AuthModule` replaces it
+with `bunPassword` — native bcrypt through `Bun.password` — whenever
+`emailAndPassword` is enabled and you did not supply a `password` of your own. That is
+Rule 1's first half: if Bun ships it, use Bun.
+
+Bun pre-hashes the input, so bcrypt's 72-byte cap is a non-issue even for a
+maximum-length multibyte password, and `verify` reads a hash from another algorithm as
+a clean authentication failure rather than a 500.
+
+**Migrating an existing user table?** Those users' scrypt hashes will no longer verify
+and they will have to reset their passwords. Pass your own `emailAndPassword.password`
+to keep the old hasher, or a hybrid that tries both.
+
+## Sessions in Redis
+
+```ts
+import { redisStorage } from '@dunx/auth';
+
+AuthModule.forRootAsync({
+  useFactory: (redis: RedisConnection) => ({
+    secondaryStorage: redisStorage(redis),
+    ...
+  }),
+  inject: [RedisConnection] as const,
+});
+```
+
+Sessions, verification values and rate-limit counters then live in Redis instead of
+costing a database round trip per request.
+
+All five methods are implemented, not the three that are mandatory. `getAndDelete` and
+`increment` are optional in better-auth's interface because most clients cannot do
+them atomically — `Bun.RedisClient` can, through `GETDEL` and `INCR`. Without them
+better-auth falls back to read-then-delete for single-use credentials, which is a
+race, and to a non-atomic rate-limit counter.
+
+`redisStorage` takes a `RedisStore`, which is six methods restated rather than
+imported — an `@dunx/infra/redis` `RedisConnection` satisfies it structurally, and so
+does anything else shaped like `Bun.RedisClient`.
+
+## What is bound
+
+`AuthModule` binds four things and mounts one controller:
+
+| Token         | Resolves to                                                     |
+| ------------- | --------------------------------------------------------------- |
+| `AuthOptions` | The resolved options, the `basePath`, and the mount path         |
+| `Auth`        | The better-auth instance                                        |
+| `AuthContext` | The per-request principal store                                 |
+| `SessionGuard`| The guard, ready for `middleware: [...]` or `@UseGuards`         |
+
+Every one of them declares its own `inject` list, so none of it needs
+`@dunx/transform`'s transform to have run — `@dunx/auth` works in an app with no
+preload.

package/dist/auth.d.ts

@@ -0,0 +1,42 @@
+import type { Auth as Instance, BetterAuthOptions } from 'better-auth';
+/**
+ * The injection token for the better-auth instance, and the whole of dunx's
+ * contract with the library.
+ *
+ * `betterAuth()` returns a plain object, so there is no class to use as a token.
+ * This is the same trick `Logger` and `RequestContext` use in `@dunx/core`: an
+ * abstract class whose members are **aliases of better-auth's own** — not
+ * restatements — which a real instance satisfies structurally. That is what makes
+ * `constructor(private readonly auth: Auth)` work, since `@dunx/transform` records
+ * the bare type name and the container resolves it.
+ *
+ * The type argument is the `DbModule` trick from `@dunx/infra/db`: the token is the
+ * erased class, so `Auth<typeof authOptions>` at an injection site keeps the
+ * plugin-widened `api` while still resolving the one binding. Written bare, `Auth`
+ * carries better-auth's core endpoints only — a plugin's endpoints are on the
+ * annotation, not on the token.
+ */
+export declare abstract class Auth<O extends BetterAuthOptions = BetterAuthOptions> {
+    /**
+     * `abstract` stops TypeScript constructing this, but the container works on
+     * runtime values and every class self-binds — so `get(Auth)` with nothing bound
+     * would hand back a bare instance whose every member is `undefined`, and the
+     * first symptom would be `auth.handler is not a function` deep in a request.
+     */
+    constructor();
+    /** better-auth's framework-agnostic handler. `AuthHandler` mounts it. */
+    abstract readonly handler: Instance<O>['handler'];
+    /** Every endpoint as a callable — `api.getSession`, `api.signUpEmail`, ... */
+    abstract readonly api: Instance<O>['api'];
+    /** The options `betterAuth()` was called with, dunx's defaults already applied. */
+    abstract readonly options: Instance<O>['options'];
+    abstract readonly $ERROR_CODES: Instance<O>['$ERROR_CODES'];
+    abstract readonly $context: Instance<O>['$context'];
+    abstract readonly $Infer: Instance<O>['$Infer'];
+}
+/**
+ * `{ session, user }` for an authenticated caller — better-auth's own inferred
+ * session type, so a plugin's extra user fields (the `admin` plugin's `role` and
+ * `banned`, say) are typed without dunx naming a single one of them.
+ */
+export type Principal<O extends BetterAuthOptions = BetterAuthOptions> = Instance<O>['$Infer']['Session'];

package/dist/context.d.ts

@@ -0,0 +1,45 @@
+import { RequestContext } from '@dunx/core';
+import type { BetterAuthOptions } from 'better-auth';
+import type { Principal } from './auth.js';
+/**
+ * How the authenticated caller reaches a handler — and anything the handler calls,
+ * however deep.
+ *
+ * `AsyncLocalStorage`, for the same reason `@dunx/core`'s `RequestContext` is: it is
+ * a Node built-in Bun implements natively, and it is the only mechanism that gets a
+ * value from middleware to a service three constructor hops away without passing
+ * it. The alternatives were both worse — request-scoped DI was measured and rejected
+ * (docs/ARCHITECTURE.md), and hanging the principal off `req` reaches a route
+ * handler but nothing a route handler calls.
+ *
+ * It is a **second** store rather than a key in `RequestContext`. That store is the
+ * log record: every field in it is serialized into every line the request writes, so
+ * a session object there would be noise on each entry and a redaction hazard in the
+ * ones that matter. What does go there is `userId` — a well-known `RequestFields`
+ * key — so the log lines are correlated without carrying the principal.
+ */
+export declare class AuthContext {
+    #private;
+    private readonly context;
+    constructor(context: RequestContext);
+    /**
+     * The caller, or `undefined` on an anonymous request. The type argument is the
+     * options object `AuthModule` was configured with, and is how a plugin's extra
+     * user fields become visible:
+     *
+     * ```ts
+     * const principal = this.auth.current<typeof authOptions>();
+     * ```
+     */
+    current<O extends BetterAuthOptions = BetterAuthOptions>(): Principal<O> | undefined;
+    /** The caller, or a 401. For a handler behind `SessionGuard` that is not `@Public()`. */
+    require<O extends BetterAuthOptions = BetterAuthOptions>(): Principal<O>;
+    /**
+     * Runs `callback` with `principal` as the caller. `SessionGuard` is what calls
+     * this; a job or a socket handler that resolved a session itself can too.
+     *
+     * `userId` is written to `RequestContext` as well, which is what puts it on every
+     * log line the callback produces.
+     */
+    run<T>(principal: Principal, callback: () => T): T;
+}

package/dist/drizzle.d.ts

@@ -0,0 +1,41 @@
+import { drizzleAdapter, type DrizzleAdapterConfig } from 'better-auth/adapters/drizzle';
+/**
+ * The two members of `@dunx/infra/db`'s `DbConnection` this reads.
+ *
+ * Restated structurally rather than imported, for the same reason `@dunx/http`
+ * restates Standard Schema: it keeps `@dunx/auth`'s dependency list at `@dunx/core`
+ * and `@dunx/http`, and it means a bare `drizzle({ client, schema })` handle works
+ * here too. An `@dunx/infra/db` connection satisfies it with no adapter in between —
+ * `dialect` is exactly that union and `db` is exactly `unknown`.
+ */
+export interface DrizzleSource {
+    readonly dialect: 'postgres' | 'mysql' | 'mariadb' | 'sqlite';
+    /** The drizzle handle — `BunSQLiteDatabase` or `BunSQLDatabase`. */
+    readonly db: unknown;
+}
+/**
+ * better-auth's `database` option over a connection the app already opened. Nothing
+ * here connects: the point is that the app keeps **one** pool, one SQLite handle and
+ * one shutdown path, instead of better-auth opening a second.
+ *
+ * ```ts
+ * AuthModule.forRootAsync({
+ *   useFactory: (connection: DbConnection) => ({
+ *     database: drizzleDatabase(connection),
+ *   }),
+ *   inject: [DbConnection],
+ * });
+ * ```
+ *
+ * The `provider` comes from the connection's own dialect, so swapping `bun:sqlite`
+ * for `Bun.SQL` needs no edit at the call site. The schema does not have to be passed
+ * either — `@dunx/infra/db` builds its handle with `drizzle({ client, schema })` and
+ * the adapter reads `db._.fullSchema`, so the better-auth tables being in the app's
+ * schema object is the whole requirement.
+ *
+ * dunx ships **no** schema for those tables. They are better-auth's, they change with
+ * its plugins, and its own CLI generates them: `bunx @better-auth/cli generate`. A
+ * copy of them inside a framework is a copy that silently rots against the library
+ * that reads it.
+ */
+export declare const drizzleDatabase: (connection: DrizzleSource, config?: Omit<DrizzleAdapterConfig, 'provider'>) => ReturnType<typeof drizzleAdapter>;