drizzle-responses-and-errors

Run drizzle-kit with --output json and parse stdout as JSON, then switch on the status field. Exit code 0 means ok or no_changes, exit 1 means error, and exit 2 means missing_hints.

The missing_hints status exits with code 2 and carries an unresolved array of items needing decisions, such as rename_or_create or confirm_data_loss. Resolve each hint and retry the command; the resolution loop is covered by the drizzle-hints skill.

Yes, the SDK functions generate, push, and check return the same discriminated envelope the CLI prints with --output json. Decoding logic written for one surface works on the other, though SDK callers only see the envelope, not exit codes.

The database_driver_error code means the driver could not connect, usually due to a missing or version-mismatched package. Check meta.packages for the required npm packages and meta.note for connection hints such as SSL requirements.

This error fires when the diff would emit DDL the target dialect cannot execute, discriminated by meta.kind. Variants include drop_pk_dependency and fk_target_not_unique on MySQL, and rename_blocked_by_check_constraint or rename_schema_unsupported on MSSQL, each with a specific remediation.