Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error #1

Open
ipstas opened this issue Jun 23, 2015 · 7 comments
Open

error #1

ipstas opened this issue Jun 23, 2015 · 7 comments

Comments

@ipstas
Copy link

ipstas commented Jun 23, 2015

Tried the mmongo and got:

/usr/local/lib/node_modules/mmongo/mmongo.js:99
  var ret = child_process.spawnSync('meteor', args);
                          ^
TypeError: Object #<Object> has no method 'spawnSync'
    at getMeteorMongoUrl (/usr/local/lib/node_modules/mmongo/mmongo.js:99:27)
    at main (/usr/local/lib/node_modules/mmongo/mmongo.js:26:14)
    at Object.<anonymous> (/usr/local/lib/node_modules/mmongo/mmongo.js:161:1)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:349:32)
    at Function.Module._load (module.js:305:12)
    at Function.Module.runMain (module.js:490:10)
    at startup (node.js:121:16)
    at node.js:764:3
@skagedal
Copy link
Owner

Hi, thank you for reporting this. I realize now that mmongo needs a Node.js
version of at least 0.12 to run. I should mention in the docs.

Regards, Simon

tisdag 23 juni 2015 skrev ipstas notifications@github.com:

Tried the mmongo and got:
'''
/usr/local/lib/node_modules/mmongo/mmongo.js:99
var ret = child_process.spawnSync('meteor', args);
^
TypeError: Object # has no method 'spawnSync'
at getMeteorMongoUrl (/usr/local/lib/node_modules/mmongo/mmongo.js:99:27)
at main (/usr/local/lib/node_modules/mmongo/mmongo.js:26:14)
at Object. (/usr/local/lib/node_modules/mmongo/mmongo.js:161:1)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:349:32)
at Function.Module._load (module.js:305:12)
at Function.Module.runMain (module.js:490:10)
at startup (node.js:121:16)
at node.js:764:3
'''


Reply to this email directly or view it on GitHub
#1.

@bmlyon
Copy link

bmlyon commented Oct 1, 2015

But Meteor doesn't support 0.12, they're stuck on 0.10.40, so how would that work?

@skagedal
Copy link
Owner

skagedal commented Oct 3, 2015

You run mmongo with a regular installation of Node.js, not with the one that comes installed with Meteor. mmongo is really just a wrapper that invokes meteor and mongo; it could just as well have been written as a shell script.

@skagedal
Copy link
Owner

skagedal commented Oct 3, 2015

README updated.

@bmlyon
Copy link

bmlyon commented Oct 4, 2015

So I guess I will never be able to run mmongo on the same machine as meteor until meteor gets updated to use a newer version of node?

@skagedal
Copy link
Owner

skagedal commented Oct 4, 2015

There should be no problem with that. It is, of course, the situation for which I developed mmongo, and worked fine for me. Meteor uses its own installation of Node.js and does not care what is otherwise installed on your machine.

I have, however, only tested mmongo with Meteor 1.1 and NodeJS 0.12. If you're having issues with later versions, please do report them.

@bmlyon
Copy link

bmlyon commented Oct 4, 2015

From what I understand that may cause trouble with global installs, fibers, certain modules, and other stuff. I guess I'll give it a try and hope that I don't run into issues. Thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants