Handle "There are no migrations to run" error about migrate-mongoose HOT 4 CLOSED

@rosesonfire a quickie here:

....
return migrator.run('up')
                    .then(successfulMigration => {
                        resolve(successfulMigration);
                    })
                    .catch(err => {
                        if (err.toString() === "Error: There are no migrations to run") {
                            console.warn("There are no migrations to run");
                            resolve();
                        } else {
                            reject(err);
                        }
                    });

or same thing using async/await + try/catch.

But yes this definitely should NOT be an throw Error(), but a warning

from migrate-mongoose.

Looks great! But I don't want to write up a js script for this. I just want to use the migrate CLI. Yes, this should be a warning, not an error. Or whether it should throw an error or a warning should be configurable.

from migrate-mongoose.

@rosesonfire agreed. @balmasi will you take a look at the PR if I submit one? cuz I see there's bunch of pending PRs and I'm not sure if you're still willing to maintain the repo.

from migrate-mongoose.

Released in 4.0.0

I appreciate bringing this to my attention!

from migrate-mongoose.