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-dev-exitprocess

v0.1.6

Published

The grunt command line interface.

Downloads

5

Readme

grunt-cli Build Status

The grunt command line interface.

Install this globally and you'll have access to the grunt command anywhere on your system.

npm install -g grunt-cli

Note: The job of the grunt command is to load and run the version of grunt you have installed locally to your project, irrespective of its version. Starting with grunt v0.4, you should never install grunt itself globally. For more information about why, please read this.

See the grunt Getting Started guide for more information.

Shell tab auto-completion

To enable bash tab auto-completion for grunt, add the following line to your ~/.bashrc file. Currently, the only supported shell is bash.

eval "$(grunt --completion=bash)"

Installing grunt-cli locally

If you don't have administrator rights, you may need to install grunt-cli locally to your project using npm install grunt-cli --save-dev. Unfortunately, this will not put the grunt executable in your PATH. You'll need to specify its explicit location when executing it, eg: ./node_modules/.bin/grunt,

Note: Using grunt-cli in this way is unsupported.