Which version of mup is being picked up

$npm install -g mup

The above install picks up the

or the original

When in doubt run:

meteor npm view mup

then look at the returned repository section (which in this case points to https://github.com/kadirahq/meteor-up.git).

Thanks Huge good to know, but I am struggling a bit to configure the mup.js

as well as updating to now complains about


ReferenceError: FutureTasks is not defined

module.exports = {
  servers: {
    one: {
      host: '',
      username: 'root',
      pem: "~/.ssh/id_rsa"
      // password: '12345'
      // or leave blank for authenticate from ssh-agent

  meteor: {
    name: 'spark2acs',
    path: '..',
    servers: {
      one: {}
    buildOptions: {
      serverOnly: true
    env: {
      ROOT_URL: 'http://localhost:3000',
      MONGO_URL: 'mongodb://@localhost:27017/name'

    //dockerImage: 'kadirahq/meteord'
    deployCheckWaitTime: 60

  mongo: {
    oplog: true,
    port: 27017,
    servers: {
      one: {},

At what point is mup complaining about that?
More specifics would be useful. Issues with fibers seems to be fairly common after upgrades in meteor version, or when deploying to production servers with differences in OS, node version, or npm version.

Commonly, updating meteor changes the node version used, so you will get not very clear errors on the production server until you set the node version there to be correct for the meteor version. I believe Meteor 1.4 is using Node 4.4.7

$mup setup

returns nothing

so I dont even know what is happening. Whereas mupx provides SUCCESS etc at each level, also how to switch current version of node in Win 7? Chocolatey?

I have Win 7 with

$ node -v

which may not be stable enough version for mup or mupx deployment?

So if I :

upgrade to 1.4 -> mup then nodeVersion 4.4.7 ?
remain at 1.3 -> mupx then nodeVersion 0.10.40 ?