Node 4.1.2 Error messages

[Lewiscowles1986]

So it looks like a number of us got confused and followed mean docs, which oddly enough tells us to install mean-cli, rather than mean

linnovate/mean#1341

is there a good reason we should use mean-cli?
why will mean-cli still run even if we get errors building kerberos.o?
What are the side-effects of not having this kerberos.o?

[steezeburger]

MEAN is the "framework" - the directory structure and boilerplate. MEAN CLI is the tool used to scaffold this framework.

"The MEAN CLI is a simple Command Line Interface for installing and managing MEAN applications. As a core module of the Mean.io project, it provides a number of useful tools to make interaction with your MEAN application easier, with features such as: scaffolding, module creation and admin, status checks, and user management."

[Lewiscowles1986]

Thank you,

The main problem was not understanding what MEAN does (although thanks for letting me in on what it is the MEAN CLI is meant for). It's that the MEAN docs should cover installing MEAN, or point at this repo, and explain, hey, no need to install MEAN; just head over to MEAN CLI.

It was hugely confusing to be directed to install a package without it being explained how the process works.

I'd still also like any ideas about the kerberos.o build failing and effects on MEAN-CLI?

I'm not looking for a fix btw, I just noticed very few issues on this repo, and a few MEAN-CLI issues on the MEAN GitHub (which I imagine is a pain).

I am also not willing to downgrade Node to try MEAN, which is the only remittance advice I have seen on this issue; I can just wait until it's fixed as I don't use it for work, or have much experience in NodeJS. But I have also been contacting the outdated deps GitHub's so I can see if I can help at all; or feed any information back here.

😉