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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-npm-check-updates2

v1.0.8

Published

grunt-npm-check-updates2

Readme

grunt-npm-check-updates2 is a grunt task for running the ncu command without having to install npm-check-updates as a global package.

Installation

First install the package by running the following command:

npm install grunt-npm-check-updates2 -D

Then load the task in your Gruntfile.js:

grunt.loadNpmTasks('grunt-npm-check-updates2');

Usage

module.exports = function (grunt)
{
    grunt.initConfig({
        check_package_update2: {
            superdup: {
                options: {
                    loglevel: 'silly',
                    upgrade: true,
                    upgradeAll: true,
                    cli: true,
                    newest: true,
                    filter: '/^(myprefix-).*$/'
                }
            }
        }
    });
};

Options

The grunt task accepts the same parameters as the ncu command:

filter             include only package names matching the given string, 
                         comma-delimited list, or regex
global             check global packages instead of in the current project
help               output usage information
packageManager     npm or bower (default: npm)
registry           specify third-party NPM registry
upgrade            overwrite package file
reject             exclude packages matching the given string, comma-
                         delimited list, or regex
version            output the version number

Advanced Options

Do not use these unless you know what you are doing! Not needed for typical usage.

dev                check only devDependencies
error-level        set the error-level. 1: exits with error code 0 if no
                         errors occur. 2: exits with error code 0 if no
                         packages need updating (useful for continuous
                         integration)
jsonAll            output new package file instead of human-readable
                         message
jsonUpgraded           output upgraded dependencies in json
loglevel           what level of logs to report: silent, error, warn, 
                         info, verbose, silly (default: warn)
prod               check only dependencies (not devDependencies)
packageData            include stringified package file (use stdin instead)
packageFile            package file location (default: ./package.json)
packageFileDir         use same directory as packageFile to compare against 
                         installed modules. See #201.
newest             find the newest published versions available instead 
                         of the latest stable versions
optional           check only optionalDependencies
peer                   check only peerDependencies
silent             don't output anything (--loglevel silent)
semverLevel            find the highest version within "major" or "minor"
greatest           find the highest versions available instead of the
                         latest stable versions
upgradeAll         include even those dependencies whose latest
                         version satisfies the declared semver dependency
removeRange            remove version ranges from the final package version
timeout                a global timeout in ms