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

rollup-quickstart

v1.0.0

Published

Quickstarter project for building packages with rollup

Readme

rollup-quickstart

This package provides a simple quickstarter setup for rollup projects. It's heavily inspired by the official rollup-starter-project package but it has some small changes. The biggest chance for now is using AVA as a test runner along with the latest rollup watch package for incremental builds. In addition you can import your own modules with relative paths. Just take a look at the files in the src directory.

Just like the original package, it features babel which compiles your code written in ES 2015 and beyond.

Usage

Usage in a browser/ External dependencies

When building a package for the browser, you probably don't want to rely on external dependencies. Just unset the external property in rollup.config.js to include all modules.

To include packages from npm written as a ES2015 or CommonJS module, you could use a rollup config like this:

import babel from 'rollup-plugin-babel';
import babelrc from 'babelrc-rollup';
import includePaths from 'rollup-plugin-includepaths';
import commonjs from 'rollup-plugin-commonjs';
import nodeResolve from 'rollup-plugin-node-resolve';

const includePathOptions = {
    paths: ['src'],
    extensions: ['.js', '.json', '.html']
};
export default {
  entry: 'src/index.js',
  plugins: [
    includePaths(includePathOptions),
    babel(babelrc()),
    nodeResolve({ jsnext: true, main: true }),
    commonjs()
  ],
  targets: [
    {
      dest: pkg['main'],
      format: 'umd',
      moduleName: 'rollupQuickstart',
      sourceMap: true
    },
    {
      dest: pkg['jsnext:main'],
      format: 'es6',
      sourceMap: true
    }
  ]
};

For more information, please take a look at the rollup-plugin-node-resolve and rollup-plugin-commonjs plugin.

Structure

Source code

The source code can be found in the src directory. Because of the rollup-plugin-includepaths plugin, you can import your dependencies there with relative paths, so no ./ is required at the beginning. The index.js is the main and entry file of you package, where you'll import all other modules.

Bundled code

The bundled and compiled code lies in the dist directory. Two versions can be found there, one file with .mjs filetype (ES2015 module) and one with .js (UMD module).

Tests

The tests can be run by typing npm test. The test runner executing these tests is AVA, which works pretty well with ES2015 code. To follow best practices when writing the test, an eslint config for AVA is also provided.