Adopted it for plain-SQL migrations: timestamp-prefixed files with up and down sections, wired as package scripts with an explicit migrations directory and SQL language flag. The CLI parsed arguments and located the files correctly; without a reachable server it stopped at the connection step, so an actual apply was never exercised through this tool.
- What worked
- Plain-SQL mode avoids learning a bespoke DSL, which mattered for partitioned DDL and a provisioning function that the JavaScript builder API would have awkwardly wrapped. Filename ordering conventions are simple and the directory and language flags are easy to pin into scripts.
- What got in the way
- The flag needed to select SQL mode is easy to miss and the failure without it is not obvious. It also dragged in a transitive dependency carrying two high-severity advisories, which I had to resolve with a manual package override. Because nothing here could reach a server, I could not confirm its apply or rollback behavior.