Back-ticks instead of Single Quotes, and failed Create

[nodeGarden]

I noticed that with:

npm install -g iron-meteor

It is installing v.1.8.1, which has an issue with the execSync call having back-ticks instead of single quotes.

vagrant@ut64base:~$ iron create newProject

/usr/lib/node_modules/iron-meteor/lib/tools/meteor.js:31
    this.execSync(`meteor create ${name} --bare`, {cwd: opts.cwd, silent: true
                  ^
SyntaxError: Unexpected token ILLEGAL
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/lib/node_modules/iron-meteor/lib/tools.js:10:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)

Fixing that manually, and it dies while creating a new project still.

vagrant@ut64base:~$ iron create newProject
created newProject
created newProject/.iron
created newProject/.iron/config.json
created newProject/bin
created newProject/bin/.gitkeep
created newProject/build
created newProject/build/.gitkeep
created newProject/build/README
created newProject/config
created newProject/config/.gitkeep
created newProject/config/development
created newProject/config/development/env.sh
created newProject/config/development/settings.json
created newProject/config/production
created newProject/config/production/env.sh
created newProject/config/production/settings.json


/usr/lib/node_modules/iron-meteor/node_modules/fibers/future.js:313
						throw(ex);
						      ^
Error: Command failed: /bin/sh: 1: meteor: not found
    at Object.Future.wait (/usr/lib/node_modules/iron-meteor/node_modules/fibers/future.js:449:15)
    at Command.execSync (/usr/lib/node_modules/iron-meteor/lib/tools/exec_sync.js:22:17)
    at Command.createEmptyMeteorProject (/usr/lib/node_modules/iron-meteor/lib/tools/meteor.js:31:10)
    at /usr/lib/node_modules/iron-meteor/lib/commands/init.js:63:10
    at Object.CurrentConfig.withValue (/usr/lib/node_modules/iron-meteor/lib/config.js:65:13)
    at Command.<anonymous> (/usr/lib/node_modules/iron-meteor/lib/commands/init.js:58:24)
    at Command.invoke (/usr/lib/node_modules/iron-meteor/lib/command.js:111:26)
    at Command.<anonymous> (/usr/lib/node_modules/iron-meteor/lib/commands/create.js:15:37)
    at Command.invoke (/usr/lib/node_modules/iron-meteor/lib/command.js:111:26)
    at Command.run (/usr/lib/node_modules/iron-meteor/lib/command.js:91:21)
    - - - - -

    at ChildProcess.exithandler (child_process.js:658:15)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Process.ChildProcess._handle.onexit (child_process.js:833:5)

I see that the master branch here however is 1.8.0, so I manually installed that version

npm install -g [email protected]

Same issue though. I've tried removing and installing down to 1.7.0 and all the same

Node and NPM versions:

vagrant@ut64base:~$ node --version && npm --version
v0.10.46
2.15.1

This is a brand new instance of https://app.vagrantup.com/protean/boxes/UT64-fend vagrant box... both with and without any system upgrades.