Drizzle schema not passed to DB instance in new project

[joaodematte]

First of all, thank you — I really love this project!

When creating a new project using Drizzle as the ORM, the generated setup does not pass the schema to the Drizzle instance. As a result, TypeScript inference fails and Drizzle reports that the schema generic is missing.

Adding the schema import and passing it to the Drizzle config resolves the issue:

 import { drizzle } from 'drizzle-orm/node-postgres';
+import * as schema from './schema/auth';

-export const db = drizzle(process.env.DATABASE_URL ?? '');
+export const db = drizzle(process.env.DATABASE_URL ?? '', {
+  schema,
+});

After this change, Drizzle correctly infers table types and .query.<tableName> becomes available.

Is this really an issue, or is this the intended behavior for the project?

[linear]

BET-242

[AmanVarshney01]

can you share your bts.json or the reproducible command?

[joaodematte]

sure, here it is:

{
  "$schema": "https://r2.better-t-stack.dev/schema.json",
  "version": "3.6.5",
  "createdAt": "2025-12-02T18:32:40.244Z",
  "database": "postgres",
  "orm": "drizzle",
  "backend": "self",
  "runtime": "none",
  "frontend": [
    "tanstack-start"
  ],
  "addons": [
    "turborepo",
    "biome"
  ],
  "examples": [],
  "auth": "better-auth",
  "packageManager": "bun",
  "dbSetup": "docker",
  "api": "trpc",
  "webDeploy": "none",
  "serverDeploy": "none"
}

[Hamed-Ajaj]

i have the same problem

// Better-T-Stack configuration file
// safe to delete

{
  "$schema": "https://r2.better-t-stack.dev/schema.json",
  "version": "3.7.3",
  "createdAt": "2025-12-08T08:48:18.617Z",
  "database": "postgres",
  "orm": "drizzle",
  "backend": "self",
  "runtime": "none",
  "frontend": [
    "tanstack-start"
  ],
  "addons": [
    "turborepo"
  ],
  "examples": [],
  "auth": "better-auth",
  "payments": "none",
  "packageManager": "bun",
  "dbSetup": "docker",
  "api": "none",
  "webDeploy": "none",
  "serverDeploy": "none"
}

so the fix was :

import { drizzle } from "drizzle-orm/node-postgres";
+ import * as schema from "./schema"

export const db = drizzle(process.env.DATABASE_URL || "", {
+  schema
});

and for /schema/index.ts

export * from "./auth";

if you don't mind i can make a PR to fix it?

[AmanVarshney01]

what the best way to do this for multi schema folder structure?

-> import each schema?

or

create a index.ts that export all the schema? 🤔

[joaodematte]

I think creating an index.ts and exporting all the schemas from it is the better approach. The DX of the first option doesn’t feel very reliable in practice.

If the project is created using the Ultracite preset, it will conflict with Ultracite’s default settings. But that’s not really a big issue — users can simply disable those rules if needed.

• https://biomejs.dev/linter/rules/no-namespace-import/
• https://biomejs.dev/linter/rules/no-barrel-file
• https://github.com/haydenbleasel/ultracite/blob/main/packages/cli/config/core/biome.jsonc#L297

[AmanVarshney01]

seems right to me 😄

now available!