How to debug migrations?

[Veetaha]

migrate cli application spawns a new process where the migration is run. This means we cannot easily debug our migrations, since debugger only attaches to CLI process and doesn't step into child process.

Could you please fix this?

You can go without creating child processes or add a flag for debugging.

[wesleytodd]

Migrate uses commander at the moment for this. I had some other issues related to the way commander handles it's child processes for sub commands and began the move off to yargs, which handles this much better. I have just not had time to finish it. I would love a PR which fixed this in commander or here (circumventing the commander behavior), which we could use, but I cannot promise working on this myself.

The current way to circumvent this is to call migrate-up instead of migrate up. These shortcut bins are setup for this reason. Hope that helps.