Drizzle Kit 0.31.10: Runtime Support Expanded Across Node, Bun, Deno

Here at industry sources, we tracked Drizzle Kit's latest release and identified three core improvements worth your attention. The headline shift is moving from esbuild-register to tsx loader for handling module resolution. This isn't cosmetic - it changes how drizzle-kit processes your migration files and schema definitions across different JavaScript environments.

The tsx loader migration solves a real problem: esbuild-register struggled with mixed ESM and CommonJS codebases. Developers using TypeScript migrations with import statements in Node.js would hit module resolution errors. tsx, a purpose-built TypeScript executor, handles this complexity natively. You no longer need to worry about transpilation mismatch between your build pipeline and your migrations.

Alongside the loader change, Drizzle added explicit Bun and Deno support. These runtimes bypass the tsx loader entirely - they run migrations directly. This matters if you're building on Bun for performance or experimenting with Deno's security model. No forced transpilation means faster startup times for your schema updates.

• Migrated from esbuild-register to tsx loader for better ESM/CJS interop
• Added native Bun launch support - skips tsx entirely
• Added native Deno launch support - skips tsx entirely
• Updated hanji dependency to 0.0.8 with Bun-optimized string utilities

If you've written migrations as TypeScript files, you know the friction: will the tooling actually execute my imports correctly? esbuild-register made assumptions about your project structure. tsx doesn't - it's specifically designed to execute TypeScript exactly as your runtime would, after proper transformation.

The practical impact: your migration files now have fewer surprises. If your project imports from ESM packages, your migrations can too. If you use CommonJS requires, those work. If you mix both (not ideal, but it happens), tsx handles it. This reduces the gap between 'runs in my editor' and 'runs in CI/CD'.

For teams using Bun or Deno, the native support is performance-relevant. Bun's migration execution is now direct - no tsx intermediary. Deno gets the same treatment. These runtimes are getting traction for their speed and security properties. Having drizzle-kit work natively means you're not adding transpilation overhead to what should be a fast operation.

• TypeScript migrations now execute with consistent module resolution across Node, Bun, Deno
• Reduces transpilation mismatches that can cause migration failures in CI
• Bun and Deno users get direct execution without intermediary loaders
• Lower cognitive load: migration failures are less likely to be tooling-related

The hanji dependency bump adds Bun-optimized string width and ANSI stripping. More importantly, it includes error handling for non-TTY environments. This matters more than it sounds: when you run drizzle-kit in GitHub Actions, Docker, or any headless CI system, there's no terminal. Output formatting that assumes a TTY will fail silently or produce garbage.

The fix ensures that drizzle-kit's CLI output works in pipelines. Your migration logs are readable in CI logs. Error messages format correctly even when there's no interactive terminal. This is table-stakes for enterprise usage - you can't have tooling that falls apart in automated environments.

The Bun-specific optimizations in hanji suggest Drizzle is taking Bun adoption seriously. If your team is exploring Bun, this signals that drizzle-kit won't be a blocker. The team is investing in the runtime, not just adding surface-level support.

• Non-TTY error handling prevents garbled output in CI/CD pipelines
• Bun-native string utilities improve performance on Bun runtime
• CLI output now reliable across all execution contexts
• Signals Drizzle's commitment to supporting alternative runtimes

If you're on [email protected], update to .10. The tsx loader is a net improvement with no breaking changes. Test your migrations in your actual CI environment - run drizzle-kit generate or drizzle-kit migrate in the same pipeline you use for deploys. Verify the output format is readable and that migrations execute cleanly.

If you use Bun or Deno, this release is a reason to commit. You now have first-class support without workarounds. If you were hesitant about adopting Bun for your project, the native drizzle-kit integration removes one obstacle.

For team leads: this update reflects a shift in tooling philosophy toward multi-runtime support. Drizzle is betting that JavaScript isn't settling on Node.js alone. If your organization is exploring Bun or Deno, this ORM will support you without friction. That's worth noting in architecture decisions. The momentum in this space continues to accelerate.

• Update to 0.31.10 and test migrations in your CI environment immediately
• If using Bun or Deno, verify native execution works for your schema
• Review migration logs in CI - hanji 0.0.8 should format output cleanly
• Use this as a data point in multi-runtime adoption decisions