grunt fails due to warnings

[fionnbharra]

When I try to perform an initial build, after running 'yo mobile', I get the following -

Warning: Task "jshint:all" failed. Use --force to continue.
Aborted due to warnings.

[timelf123]

Confirmed.

Fixed by commenting '<%= yeoman.app %>/scripts/{,*/}*.js', but then you aren't validating any of your scripts, just tests...

 jshint: {
            options: {
                jshintrc: '.jshintrc'
            },
            all: [
                'Gruntfile.js',
                //'<%= yeoman.app %>/scripts/{,*/}*.js',
                '!<%= yeoman.app %>/scripts/vendor/*',
                'test/spec/{,*/}*.js'
            ]
        },

tim@tim:~/dev/mobile$ grunt
Running "jshint:all" (jshint) task
>> 2 files lint free.

[addyosmani]

Going to take a look at this on Monday. Thanks for flagging it!

[addyosmani]

Looked into this. The current issue is that we're writing files which should be in vendor directly into /scripts and they're getting linted. We could also do a better job of not linting bower_components.

[oak-tree]

"grunt fails due to warnings" still here. many warnings. doesnt work with out -f how can i edit grunt file to skip checking some of the files?

[timelf123]

@oak-tree see my previous comment for a hack

[addyosmani]

Pushed a workaround to master. We'll get out a new release in the next week.

[christianromney]

Any update on this? Updated my generator and this issue persists... TIA

[DanielTate]

Any updates? Just tied yeoman with backbone and getting the same problem.

[napstercake]

check this link: http://stackoverflow.com/questions/4462478/jslint-is-suddenly-reporting-use-the-function-form-of-use-strict