-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 while trying a first install #446
Comments
Same for me |
@jmcollin92 @phlppn thanks for reporting. caused by some very recent commits. looking into it now. |
@fyockm karma tests are also KO and I don't know if it is related :
... Running "karma:unit" (karma) task Aborted due to warnings. |
@jmcollin92 linitng fix was easy enough. I saw that travis was failing when running the karma tests. Hoping that's related to your |
@jmcollin92 I never got the |
@fyockm what is the best way to update my config ? (I'm really a newby) |
From your project root, I would add the upstream project (if you haven't already) as: Then pull from upstream: Here's some more info: http://gitready.com/intermediate/2009/02/12/easily-fetching-upstream-changes.html Hope that helps! You can also join us on the #mean.io IRC channel if you have more questions. |
@jmcollin92 Thinking about it a little more, the instructions above apply if you forked the project on GitHub, which you probably didn't. |
It's ok for jshint and karma errors. |
The EINVAL error is due to CYGWIN environment. See : nodejs/node-v0.x-archive#6459 |
Thanks for the info @jmcollin92. When I have to use Windows, I typically prefer the Git Bash. |
Hello,
I'm a very beginner with Mean and I'm facing problems at the "grunt" step.
When a issue the grunt command, I got this error message :
Running "jshint:all" (jshint) task
server\config\express.js
180 | function themeHandler(req, res) {
^ 'themeHandler' was used before it was defined.
with -f to force it fails another time later :
...
Running "nodemon:dev" (nodemon) task
Waiting...
[nodemon] v1.0.17
Fatal error: EINVAL, invalid argument
Warning: Used --force, continuing.
Any idea to continue ?
JM.
The text was updated successfully, but these errors were encountered: