-
Notifications
You must be signed in to change notification settings - Fork 12
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
Grunt build aborts after failing JSHint #91
Comments
I forgot to mention that this only happens when I install conductor.js as a dependency using bower for another project. e.g.
|
https://github.com/stefanpenner/ember-app-kit/blob/master/tasks/options/jshint.js#L24-L27 would help, at-least for the non-CI runs. |
@stefanpenner I was successfully able to make everything work fine by doing a force initially - I'm just not sure if theres a specific reason why this would fail due to a bower install? Maybe not a big thing since its already built - but just wanted to raise the issue. |
@alvincrespo jshint will pass on the source (or at least it ought to!) but we can't get it to pass on the built file because it includes dependencies that do not pass jshint. Also we have shims taken directly from the mozilla developer network that don't pass jshint. Do you happen to know of an option for ignoring |
When running grunt build after installing npm dependencies, I get the following JSHint errors:
The text was updated successfully, but these errors were encountered: