mean status command returns ENOENT - Windows 7

[joaocampos1906]

Hi,

I've stumbled upon the mean status command and tried to run it to see it's output. But, when it tries to check for meanio command line version it returns a ENOENT error like this:

    MEAN Status
    -----------

    MEAN VERSION: 0.3.0

    MongoDB URI: mongodb://localhost/udo-db
    DB connecting successful!


    checking meanio command line version

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)

I get the same error if I try to install the mean-tokens module.

Thanks for the help!

[ellman]

Hi @joaocampos1906. I will try reproduce this on a windows machine. What version of npm are you using? npm -v Thanks

[joaocampos1906]

Using npm 1.4.3

If it helps I'm on a Windows 7 Pro- 64 bit machine.

[fyockm]

@joaocampos1906 I was able to duplicate on a Win7 VM with npm 1.4.3. I will look into it and hopefully have a remedy soon.

[joaocampos1906]

I had the same error while using mean install mean-tokens, posted the issue on mean-tokens repository but still no answer, so if you are able to replicate it as well it's probably a meanio problem and not the module itself.
Thanks for your answers 👍

[enduring-x]

same issue with me using ubuntu trying to run "mean init [myApp]"
node -v v0.10.26
npm -v 1.4.3

[joaocampos1906]

@rmaiolo Have you installed git on ubuntu? I had the same error until I remembered I was trying to clone things from git without having it installed on ubuntu. Try that, it should solve the problem.

[fyockm]

@joaocampos1906 thanks for the help on Ubuntu. I hope you are right.

I believe I've solved the issue on Windows! See SE discussion here.

I updated mean-cli locally to use process.platform === 'win32' ? 'npm.cmd' : 'npm'; and it worked successfully for me with both mean status and mean install mean-tokens. I will push a change shortly.

[enduring-x]

@joaocampos1906 that was the issue..thanks!!!

[joaocampos1906]

@fyockm Thanks! Guess I'll wait for the new mean-cli push :)
@rmaiolo No problem man, glad I helped!

[fyockm]

@joaocampos1906 I've updated mean-cli but don't have privileges to publish the update to npm, as of yet. Hope to get that remedied soon.

If you're eager to try the fix, you can clone the mean-cli repo, and then use npm link to test.

[ellman]

I just updated pushed to npm. @fyockm thanks for preparing the fix! @joaocampos1906 let us know if there are any other issues. Latest version is 0.3.9

[joaocampos1906]

Ok, so I think I've updated meanio to the latest version, which states it is 0.3.21 by using mean -V therefore is inconsistent with the version @ellman stated above. And I've created a new app, installed everything with npm install and clean the npm and bower caches and I keep getting the same error. Since @fyockm managed to solve this for himself I wonder that it might me my problem, but I don't know what is causing it.
Tried to install mean-cli localy and globaly; localy it did nothing and globaly did nothing but overwrite meanio mean commands.

[ellman]

hi @joaocampos1906 @fyockm code is merged in the latest meanio. As there are constant improvments and changes I would recommend for now using latest eg sudo npm install -g meanio@latest. once done in your mean project run mean status

[joaocampos1906]

Hi @ellman thanks for the fast answer! It worked, I'm currently on version 0.3.14 which makes more sense than 0.3.21.
The mean status and mean install mean-tokens commands ran sucessfuly. Once again thanks for the lightning speed answer and for solving my troubles!

[ellman]

@joaocampos1906 pleasure, have fun :) you can thank @fyockm for the fix.

[joaocampos1906]

Yeah, where are my manners?! Thank you very much @fyockm ! :D

[fyockm]

@joaocampos1906 You're welcome - Glad it worked for you too!