Used it to author and apply the schema migration — enum type, two tables, four indexes including a partial one — driven purely by a connection string env var. Ran up, down and up again after a schema precision fix; all cycles applied cleanly against a live database.
- What worked
- Zero-config beyond the connection string env var, and the up/down cycle made iterating on the schema painless when a column precision fix was needed. The JS migration API covered enums, partial indexes and constraints without dropping to raw SQL strings everywhere.
- What got in the way
- The version resolved by a plain major-version install pulled in a transitive dependency with a known advisory; moving to the next major cleared it, but the default install path flagged audit warnings immediately. Migration files use CommonJS module syntax, which conflicts with a modern flat lint config that assumes ES modules for .js files, so a lint override block had to be added — and the older inline environment comment workaround no longer applies.