npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lazy-grunt-loading

v0.1.1

Published

Experimental utility to load grunt tasks lazily

Downloads

4

Readme

Build Status

lazy-grunt-loading

Experimental utility to load grunt tasks lazily

The grunt workflow is to load all tasks for every invocation of grunt, then only run the ones the user actually wants. If you have a project with a ton of grunt tasks, or grunt tasks that take a long time to load, this could end up being painful. To address this pain, I've created a module that makes a few (potentially brittle) assumptions and hooks into grunt.task.run to only run the tasks you need.

Old way:

Gruntfile.js

module.exports = function(grunt) {

  // Both foo and bar will be loaded every time, even if you are not using all of them.
  grunt.loadTask('foo');
  grunt.loadTask('bar');

  grunt.initConfig() {
    foo: fooOpts,
    bar: barOpts
  }
};

New way:

Gruntfile.js

module.exports = function(grunt) {

  var lazyGruntLoading = require('lazy-grunt-loading');

      // A list of all files that could contain tasks you want to load. 
      // Getting this list is outside the scope of this module.
      // Ex: ['node_modules/foo/tasks/grunt-foo.js', 'tasks/file_name.js']
  var taskFiles = getTaskFiles(),
  
      // Optional: Not every grunt task is declared in a file of the same name. 
      // Pass an override here to get around this. This is not necessary if 
      // the only difference is the file having the 'grunt-' prefix - that
      // will get handled automatically. In this example, we see above that
      // taskFiles has 'tasks/file_name.js', which defines the 'bar' task,
      // so we add that override here.
      overrides = { file_name: 'bar'},
      
      // Optional: function to use for logging
      log = grunt.verbose.write;
  
  // Only the tasks you need will be loaded.
  lazyGruntLoading(grunt, taskFiles, overrides, log);

  // Config proceeds as it normally would.
  grunt.initConfig() {
    foo: fooOpts,
    bar: barOpts
  }
};

This could ultimately be a bad idea, but I'd like to experiment with it. Because parts of this are brittle, and getting the list of all files a task could be declared in is a burden, I don't recommend using this module unless your task load time is getting painful.