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

grunt-auto-config

v0.1.0

Published

Automatically load all grunt task's config

Downloads

4

Readme

grunt-auto-config

Automatically load all grunt plugins and their configs in a nicer way

Build Status

Getting Started

This plugin requires Grunt ~0.4.1.

In a nutshell, this plugin will load all your grunt plugins automatically by reading it from package.json file. So, you don't have to explicitly set grunt.loadNpmTasks(); in your Gruntfile anymore.

Another thing that grunt-auto-config offers you is a better grunt configs structure. Instead of having a long configuration in Gruntfile. It'll also lookup for config in ./config directory for each task.

For example, let's say you have grunt-contrib-copy plugin installed. Normally you'll have to put its config in Gruntfile like this

grunt.initConfig({
  copy: { ... }
})

With this plugin, it'll look for file ./config/copy.js (or copy.coffee) and load from that file. So, in copy.js you just have to add this.

module.exports = {
  options: ...
  target1: ...
}

You may install this plugin with this command:

npm install grunt-auto-config --save-dev

To enable this plugin, put this line of code at the end of Gruntfile:

// other stuffs
grunt.loadNpmTasks('grunt-auto-config');

The "auto_config" task

Overview

In your project's Gruntfile, add a section named auto_config to the data object passed into grunt.initConfig().

grunt.initConfig({
  auto_config: {
    options: {
      // Task-specific options go here.
    }
  },
});

Options

options.dir

Type: String Default value: ./config

A string value that is used to specify grunt config directory

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)