Gruntplugin Lazy Loading
npm install grunt-lazyloadGruntplugin Lazy Loading
_The Api has been changed to extend the grunt object, rather than provide a new wrapping object. For documentation on the old api (v0.2.2 and below) go here: v0.2.2_
npm install grunt-lazyload --save``js
require('grunt-lazyload')(grunt);
grunt.lazyLoadNpmTasks('grunt-contrib-jshint', 'jshint');
`
#### Before Lazy Loading
!Before Lazy Loading
#### After Lazy Loading
!After Lazy Loading
_(Image captured with time-grunt)_
Another big win is if you are using grunt in conjunction with Jenkins to do your deploys. If you are lazy loading npm modules, modules that wont get triggered dont even need to be installed. So when jenkins starts running a job it runs npm install --production and only downloads the production dependencies and not the dev dependencies like grunt-contrib-watch for example. This means my npm install step during my deploys dropped from about 15 seconds to about 10. This was a big win for me and my team. Even when I have a full node_modules folder the check to see if anything needs updating dropped by 250ms by running npm install --production
Not everyone is using grunt the same way, but if you want your grunt to run a little bit faster, consider lazy loading.
js
require('grunt-lazyload')(grunt);
`
This is not truly a grunt plugin, but a node module that adds extra methods to to allow lazy loading. Pass the instance of grunt you intend to extend.$3
`js
grunt.lazyLoadNpmTasks('grunt-contrib-jshint', 'jshint');
`$3
js
grunt.lazyLoadNpmTasks('grunt-some-plugin', ['task1', 'task2', 'task3']);
`$3
js
grunt.lazyLoadTasks('localdir/tasks', {
'grunt-custombuild.js': 'custombuild',
'grunt-deploy.js': ['deploy'],
'grunt-customclean.js': ['clean', 'cleanall', 'reset'],
});
`In order to initialize lazy loading, you must define ahead of time the possible task names and where to load them from. For
, specify the task (or tasks) that are provided by that NPM module. For a local directory of tasks,
provide a hash, where each key is the _exact filename_ containing the tasks, and the value is the task (or tasks) it provides.$3
`js
grunt.lazyLoadNpmTasks('grunt-contrib-copy', 'copy');
grunt.renameTask('copy', 'classic-copy');// Later
grunt.task.run('classic-copy:somefiles');
`Task renames are automatically tracked by the lazy loader and saved for later resolution. In this example, when you
attempt to run
, the lazy loader will load grunt-contrib-copy and register the copy task as classic-copy`.Automatic task renaming works for both NPM tasks and local task directories.