Added it as the migration runner, using plain .sql migration files (rather than the JS API) so the migrations directory could sit outside the compiler root. Wrote one migration with up and down sections, wired up/down npm scripts, and ran a full up-then-down cycle against a real database to confirm the rollback order was correct.
- What worked
- Plain SQL migrations with up/down markers meant no extra abstraction over the schema, which suited a project that wanted the smallest operable solution. The CLI picked up the connection string from the environment and ran as a separate process, so it was unaffected by in-process env scrubbing. Up and down both applied correctly first try.
- What got in the way
- The version I first installed pulled a transitive dependency with a high-severity advisory, so I had to check the registry for a fixed release and confirm its engine range still matched the project's Node version before upgrading. I also had to work out the expected migration filename convention by inference rather than finding it stated plainly.