Skip to content

Add Replit compatibility to Drizzle Kit RC4#29

Draft
joe-thom wants to merge 3 commits into
joe-thom/drizzle-v1-rc4-syncfrom
joe-thom/drizzle-v1-compat
Draft

Add Replit compatibility to Drizzle Kit RC4#29
joe-thom wants to merge 3 commits into
joe-thom/drizzle-v1-rc4-syncfrom
joe-thom/drizzle-v1-compat

Conversation

@joe-thom

@joe-thom joe-thom commented Jul 17, 2026

Copy link
Copy Markdown

What changed

Adds the internal @drizzle-team/drizzle-kit artifact and pid2-facing database diff API on top of Drizzle Kit RC4. It preserves capped Postgres introspection concurrency, legacy conflict resolvers, generated SQL, and structural data-loss reporting without changing the upstream workspace package identity.

Why

Pid2 needs low-level introspection and interactive diff hooks that upstream Drizzle Kit does not export. Keeping the source workspace named drizzle-kit lets upstream CI continue to operate normally, while pack:replit rewrites only the internal tarball manifest.

What changed

  • Adds the ./api CJS, ESM, and declaration bundles.
  • Adapts pid2 resolver callbacks to RC4 DDL resolvers.
  • Caps shared query and proxy concurrency through preparePgDB.
  • Preserves destructive-change classification and unique-constraint prompts.
  • Adds explicit pack:replit and publish:replit commands for the scoped internal artifact.
  • Removes bundled Brocli from only the internal manifest because Replit routes the @drizzle-team scope to Artifact Registry.

Test plan

  • pnpm lint:check
  • pnpm --filter drizzle-kit test:types
  • pnpm --dir drizzle-kit exec vitest run tests/other/replit-api.test.ts (5 passed)
  • pnpm --filter drizzle-kit pack:replit
  • Typechecked and loaded the packed artifact through CJS and ESM with drizzle-orm@0.45.2, pg@8.5.1, and @types/pg@8.15.5.
  • Installed the tarball into a disposable current repl-it-web worktree, passed the full pid2 typecheck after the expected schema-shape migration, and passed 7 focused database-diff tests.

Stack

Rollout and rollback

Do not publish until both PRs merge. Publishing and the pid2 dependency bump remain separate, explicitly gated steps. The source change is safe to revert before publication and does not modify persistent data.

~ written by Zerg 👾 (wp-961c729b)

@joe-thom joe-thom added the zergling-authored Authored by a Zerg zergling label Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

zergling-authored Authored by a Zerg zergling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant