Skip to content

The command "list" does not end the process when there are no migrations to list. #210

@brianr482

Description

@brianr482

Hi! 👋

Firstly, thanks for your work on this project! 🙂

Today I used patch-package to patch [email protected] for the project I'm working on.

I noticed that the command list stays alive forever when it does not find any migration to list.

Here is the diff that solved my problem:

diff --git a/node_modules/migrate/bin/migrate-list b/node_modules/migrate/bin/migrate-list
index d25b3b1..a8acf63 100755
--- a/node_modules/migrate/bin/migrate-list
+++ b/node_modules/migrate/bin/migrate-list
@@ -68,7 +68,8 @@ migrate.load({
   }
 
   if (set.migrations.length === 0) {
-    return log('list', 'No Migrations')
+    log('list', 'No Migrations')
+    process.exit(0)
   }
 
   set.migrations.forEach(function (migration) {

This issue body was partially generated by patch-package.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions