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-cli-config

v0.1.7

Published

Set the config with the options passed on the CLI.

Downloads

6

Readme

grunt-cli-config Build Status NPM version Dependency Status Coverage Status

Install

This plugin extends grunt to allow you to overwrite your grunt config options by invoking parameters on the command-line interface (CLI).

Usage example

After you add grunt-cli-config to your package.json or use npm install grunt-cli-config, load the plugin before you invoke its applyCliConfig method

grunt.loadNpmTasks('grunt-cli-config');

Then, on a grunt task call

var task = 'test',
    subTask = 'foo';

// e.g., grunt.applyCliConfig('build', 'calendar', 'gregorian');
grunt.applyCliConfig(task, subTask);

There's a arbitrary number of arguments you can pass to the applyCliConfig method and they should be interpreted as sub-levels of the config options.

On the CLI you can invoke commands like

$ grunt test --module calendar --no-coverage
Running "jshint:all" (jshint) task
>> 3 files lint free.
...

The module option will be set to calendar and the coverage option will be set to param.

Notice you can negate booleans by using --no-<param>.

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.

License

Licensed under the MIT license.