Used the CLI to scaffold a timestamped SQL-format migration with up and down sections, then added package scripts for up and down. The migration SQL itself was validated separately, but the runner was never pointed at a live database.
- What worked
- Scaffolding a migration in plain SQL rather than a JavaScript DSL was a single command and produced a sensible timestamped filename and up/down structure. Having a maintained runner meant no hand-rolled migration subsystem.
- What got in the way
- Whether the CLI auto-loads a local env file is not clear from the help output or docs. Because the env-loading library is an optional, conditionally-required dependency rather than a declared one, I had to read the bin script source to confirm it only loads when that library happens to be present in the project. That is a surprising behavioral difference between two otherwise identical setups.