I'm pretty sure that qualifies you as a grunt expert!

On Jul 19, 2013, at 7:10 PM, Jon Schlinkert <notifications@github.com>
wrote:

In Gruntfile.js:

> +        files: '<%= jshint.gruntfile.src %>',
> +        tasks: ['jshint:gruntfile']
> +      },
> +      lib: {
> +        files: '<%= jshint.lib.src %>',
> +        tasks: ['jshint:lib', 'nodeunit']
> +      },
> +      test: {
> +        files: '<%= jshint.test.src %>',
> +        tasks: ['jshint:test', 'nodeunit']
> +      }
> +    }
> +  });
> +
> +  // Load these plugins to provide the necessary tasks
> +  require('matchdep').filterDev('grunt-*').forEach(grunt.loadNpmTasks);

I'm definitely not a "grunt expert", but I have created about 12-15 grunt
plugins, and I've used it on > 100 projects. One of the grunt projects I
created, assemble <http://assemble.io>, is one of the most popular grunt
plugins (I think top 10?). So again I'm not claiming to know everything
about Grunt in the least, but I have more than enough experience with it to
feel good about the conventions I'm using.

—
Reply to this email directly or view it on
GitHub<https://github.com/less/less.js/pull/1431/files#r5304741>
.