node-migrate

Hello. I created the test repo on which I am testing the current library. I run command and get next output Everything works as it should but now I run and get It is not right since the migration should have rolled back too based on this quote from the documentation Similarly you can run down-migrations up to (and including) a specific migration and if after it I run which was rolled back above I get That's very strange. And the last. If we have two branches and the migrations and were created and applied in first branch, and the migration was created in the other branch, which was created earlier than , then when the second branch merges with the first and call and then everything will break down and we won’t be able to roll back to any specific migration except .

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.

supports passing multiple files as an array, but the old version of does not support variadic parameters.