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-rollup2

v1.1.1

Published

A Rollup task for Grunt

Downloads

18

Readme

Grunt rollup

A Rollup task for grunt with the ability to create multiple bundles.

This is not a fork of grunt-rollup, but is inspired by it.

Task reference

options.rollup

The Rollup module itself. This task has a peer dependency to Rollup, so you have to install it yourself. This makes the task non-dependent of a Rollup version and more flexible for future Rollup versions.

options.bundles

An array of objects which define your bundles.

options.bundles[].input

Input options for your Rollup bundle. You can find a reference of all the available options here: https://rollupjs.org/guide/en#inputoptions

The only difference here is that options.bundle[].input.plugins options should be a function that returns an array. Many plugins for Rollup are stateful and we don't want that when we are building multiple bundles.

options.bundles[].output

Output options for your Rollup bundle. You can find a reference of all the available options here: https://rollupjs.org/guide/en#outputoptions

Usage

// Gruntfile.js

const rollup = require('rollup')
const babel = require('rollup-plugin-babel')

module.exports = function(grunt) {
  grunt.initConfig({
    rollup: {
      prod: {
        options: {
          bundles: [
            {
              input: {
                input: 'src/index.js'
                plugins: () => [
                  babel()
                ],
              },
              output: {
                file: 'dist/build.js'
              }
            }
          ],
          rollup: rollup,
        },
      },
    },
  });
};

Roadmap

  • [x] Multiple bundles

  • [ ] Tests

  • [ ] Watch task efficiency. Only rebuild the bundle that got changed.

    The task currently rebuilds every bundle on a reload in any watch task, the ability to only rebuild the bundle that actually got changed would be a nice performance boost. I currently personally use https://github.com/gruntjs/grunt-contrib-watch for watch tasks, but i'd love to hear from different options.