Drizzle throws SQL type conflict - Argument of type 'SQL' is not assignable to parameter of type 'SQL

[extenv]

Drizzle throws SQL type conflict

I'm consistently getting this TypeScript error whenever I try to join two tables using Drizzle ORM:

Argument of type 'SQL<unknown>' is not assignable to parameter of type 'SQL<unknown> | ...'.
Type '.../drizzle-orm@0.45.0+49c6d5e2b5ce5aad/.../SQL<unknown>' is not assignable to type '.../drizzle-orm@0.45.0+cc127fb80b35d2e5/.../SQL<unknown>'.
Types have separate declarations of a private property 'shouldInlineParams'.

The error points to two different internal build hashes of Drizzle:

• 0.45.0+49c6d5e2b5ce5aad
• 0.45.0+cc127fb80b35d2e5

This means that Drizzle is being installed more than once inside node_modules, causing TypeScript to treat them as different types even though the versions are the same. Because the SQL class contains private fields, TypeScript sees them as incompatible, triggering the error.

even though I didn't install it again, everything is default from the template

Temporary Fix

If I run the following:

rm -rf node_modules bun.lockb
bun install

…the issue disappears—until it eventually comes back again.

Project Setup

This project was created using:

bun create better-t-stack@latest looks-good   --frontend solid   --backend hono   --runtime bun   --api orpc   --auth better-auth   --payments none   --database mysql   --orm drizzle   --db-setup docker   --package-manager bun   --no-git   --web-deploy none   --server-deploy none   --install   --addons turborepo   --examples todo

Question

Why is Bun repeatedly installing multiple internal builds of Drizzle ORM?
Is this caused by transitive dependencies, Turborepo workspaces, or something ?

Any guidance on how to prevent duplicate Drizzle installations from being generated would be appreciated.

[linear]

BET-247

[AmanVarshney01]

i have drizzle-orm in two packages - api and db but i am using catalogs so i am not sure why there are two instances 🤔

Can you try upgrading bun? (bun upgrade)

[joaodematte]

I ran into this same error when installing drizzle-orm in two separate packages (api and db). On the api side I was using Drizzle inside my tRPC procedures.

The fix was to remove drizzle-orm from the api package and rely only on the db package. By using the arrow-function query helpers, the db instance gives me access to all tables and operators (eq, ne, etc.) without needing Drizzle installed in api.

Example:

const result = await db.query.customer.findFirst({
  where: (c, { eq }) => eq(c.id, input.id),
  with: {
    addresses: true,
    salesRepresentative: true,
  },
});

[AmanVarshney01]

how to do that for update and delete?

[joaodematte]

how to do that for update and delete?

Good point — I didn’t think about that initially. From what I’ve found, those query helpers are only available on .query.