Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (drizzle-kit) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Drizzle Kit
DrizzleKit - is a CLI migrator tool for DrizzleORM. It is probably one and only tool that lets you completely automatically generate SQL migrations and covers ~95% of the common cases like deletions and renames by prompting user input. https://github.com/drizzle-team/drizzle-kit-mirror - is a mirror repository for issues.
Documentation
Check the full documenation on the website
How it works
drizzle-kit will traverse schema folder or schema file, generate schema snapshot and compare it to the previous version, if there's one.
Based on the difference it will generate all needed SQL migrations and if there are any automatically unresolvable cases like renames it will prompt user for input.
For schema file:
// ./src/db/schema.ts
import { integer, pgTable, serial, text, varchar } from "drizzle-orm/pg-core";
const users = pgTable("users", {
id: serial("id").primaryKey(),
fullName: varchar("full_name", { length: 256 }),
}, (table) => ({
nameIdx: index("name_idx", table.fullName),
})
);
export const authOtp = pgTable("auth_otp", {
id: serial("id").primaryKey(),
phone: varchar("phone", { length: 256 }),
userId: integer("user_id").references(() => users.id),
});It will generate:
CREATE TABLE IF NOT EXISTS auth_otp (
"id" SERIAL PRIMARY KEY,
"phone" character varying(256),
"user_id" INT
);
CREATE TABLE IF NOT EXISTS users (
"id" SERIAL PRIMARY KEY,
"full_name" character varying(256)
);
DO $$ BEGIN
ALTER TABLE auth_otp ADD CONSTRAINT auth_otp_user_id_fkey FOREIGN KEY ("user_id") REFERENCES users(id);
EXCEPTION
WHEN duplicate_object THEN null;
END $$;
CREATE INDEX IF NOT EXISTS users_full_name_index ON users (full_name);Installation & configuration
npm install -D drizzle-kitRunning with CLI options
// package.json
{
"scripts": {
"generate": "drizzle-kit generate:pg --out migrations-folder --schema src/db/schema.ts"
}
}npm run generateConfiguration
Instead of passing arguments to the CLI commands, you can also create a drizzle.config.json configuration file:
{
"out": "./migrations-folder",
"schema": "./src/db",
"breakpoints": false
}out- path to the output directory where migrations will be saved,schema- path to TypeScript schema file or folder with multiple schema files,breakpoints- whether to execute each statement in the migrations individually. Set totrueif you are using SQLite or MySQL (as they don't support multiple DDL statements in a transaction).
Upgrading to 0.17.0
Before running any new migrations drizzle-kit will ask you to upgrade first
Migration file structure < 0.17.0
📦 <project root>
└ 📂 migrations
└ 📂 20221207174503
├ 📜 migration.sql
├ 📜 snapshot.json
└ 📂 20230101104503
├ 📜 migration.sql
├ 📜 snapshot.jsonMigration file structure >= 0.17.0
📦 <project root>
└ 📂 migrations
└ 📂 meta
├ 📜 _journal.json
├ 📜 0000_snapshot.json
├ 📜 0001_snapshot.json
└ 📜 0000_icy_stranger.sql
└ 📜 0001_strange_avengers.sqlTo easily migrate from previous folder structure to new you need to run up command in drizzle-kit. It's a great helper to upgrade your migrations to new format on each drizzle kit major update
List of commands
Generate SQL migrations based on current .ts schema
$ drizzle-kit generate:pg $ drizzle-kit generate:mysql $ drizzle-kit generate:sqlite
--config [optional default=drizzle.config.json] config file path--schema path to typescript schema file or folder with multiple schema files--out [optional default=drizzle/] migrations folder--breakpoints [optional default=false] whether to execute each statement in the migrations individually\
$ drizzle-kit generate:pg
## runs generate command with drizzle.config.json
$ drizzle-kit generate:pg --config=./custom.config.json
## runs generate command with custom.config.json
$ drizzle-kit generate:pg --schema=./src/schema.ts
## runs generate command and outputs results to ./drizzle
$ drizzle-kit generate:pg --schema=./src/schema.ts --out=./migrations/
## runs generate command and outputs results to ./migrationGenerate an empty SQL migration with --custom
$ drizzle-kit generate:pg --custom
## runs generate command and outputs an empty migration for custom SQLIntrospect existing database and generate typescript schema
$ drizzle-kit introspect:pg $ drizzle-kit introspect:mysql
drizzle-kit introspect:pg --out=migrations/ --connectionString=postgresql://user:pass@host:port/db_name
drizzle-kit introspect:pg --out=migrations/ --host=0.0.0.0 --port=5432 --user=postgres --password=pass --database=db_name --ssl
Update stale snapshots
$ drizzle-kit up:pg $ drizzle-kit up:mysql $ drizzle-kit up:sqlite
--out [optional] migrations folder--config [optional default=drizzle.config.json] config file path
## migrations folder is taken from drizzle.config.json
drizzle-kit up:mysql
drizzle-kit up:mysql --out=migrations/
Drop migration
$ drizzle-kit drop
--out [optional] migrations folder--config [optional default=drizzle.config.json] config file path

Migrations collisions check
$ drizzle-kit check:pg $ drizzle-kit check:mysql $ drizzle-kit check:sqlite
--out [optional] migration folder--config [optional default=drizzle.config.json] config file path
## migrations folder is taken from drizzle.config.json
drizzle-kit check:pg
drizzle-kit check:pg --out=migrations/