0.10.0-beta.1 does fail if a local version lower than 0.10.0 is installed

[suomi35]

The following will produce the below error:
npm install -g db-migrate && db-migrate down && db-migrate up

Error:
-e/rof/.nvm/v0.10.40/bin/db-migrate -> /home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/bin/db-migrate
db-migrate@0.10.0-beta.1 /home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate
parse-database-url@0.2.2
async@1.4.2
dotenv@1.2.0
pkginfo@0.3.0
semver@5.0.3
mkdirp@0.5.1 (minimist@0.0.8)
optimist@0.6.1 (wordwrap@0.0.3, minimist@0.0.10)
final-fs@1.6.1 (node-fs@0.1.7, when@2.0.1)
resolve@1.1.6
bluebird@2.10.2
tunnel-ssh@2.0.0 (debug@2.2.0, lodash@3.10.1, ssh2@0.4.11)
moment@2.10.6

/home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/bin/db-migrate:21
dbmigrate = DBMigrate.getInstance();
^
TypeError: Object # has no method 'getInstance'
at /home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/bin/db-migrate:21:25
at /home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/node_modules/resolve/lib/async.js:44:21
at ondir (/home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/node_modules/resolve/lib/async.js:187:31)
at onex (/home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/node_modules/resolve/lib/async.js:93:22)
at /home/rof/.nvm/v0.10.40/lib/node_modules/db-migrate/node_modules/resolve/lib/async.js:24:18
at Object.oncomplete (fs.js:108:15)

[wzrdtales]

@suomi35 Thank you for reporting.
Is it possible that you have installed locally a db-migrate version that is lower than 0.10.x?

If yes, db-migrate always prefers from 0.10.x on the local installed version. v0.9.x does not have the getInstance singleton and this would explain this failure.

This behavior is also mentioned within the breaking changes:
#315

[wzrdtales]

With local I do mean an installation within your project you try to execute the migrations from.

[wzrdtales]

I think I will make the startup script recognize if versions are lower than 0.10.0, so that no one has to run in this kind of issue.

[suomi35]

Thanks for the prompt attention! I am building a virtual machine via codeship and installing db-migrate in sequence with some other modules. So it should be pulling from the internet every time since codeship blows it away upon each push.
I read #315 and decided to modify as follows to grab the driver, but still get the same error:
npm install -g db-migrate && npm install -g db-migrate-pg && db-migrate down && db-migrate up

[wzrdtales]

Ok, does your project package.json include a lower db-migrate version than 0.10.x?

[suomi35]

"db-migrate": "^0.9.23" oops ;)

[wzrdtales]

Yes this is the failure here. DBMigrate recognizes this and calls the 0.9.23 instead of your local project. Update this one 0.10 or just completely remove it. I will publish a patch shortly which ignores your local version if it is lower than 0.10.x and also displays an information if the local version is used.

[suomi35]

Thanks so much for the assist!

[wzrdtales]

@suomi35 My pleasure, whenever you have another question feel free to ask.