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

gobble-test

v0.1.1

Published

Utility for testing gobble plugins

Readme

gobble-test

This is a simple utility for testing gobble plugins.

Installation

npm i -D gobble-test

Usage

(Note: these instructions are guidelines only. Feel free to adapt to your circumstances.)

In your plugin repo, create a test directory. Inside that folder create two subdirectories - src and expected - and an index.js file, so that your plugin repo looks something like this:

gobble-myplugin
|- test
   |- src
   |- expected
   |- index.js
|- package.json
|- index.js
|- README.md

In the src directory, create some source files. In the expected directory, create a directory of output files for each test. Your index.js file should look something like this:

var gobble = require( 'gobble' ),
    test = require( 'gobble-test' ),
    path = require( 'path' ),
    myPlugin = require( '../' );

test([
  {
    name: 'myplugin without options',
    definition: gobble( path.join( __dirname, 'src' ) ).transform( myplugin ),
    expected: path.join( __dirname, 'expected/no-options' )
  },
  {
    name: 'myplugin with some options',
    definition: gobble( path.join( __dirname, 'src' ) ).transform( myplugin, {
      foo: 'bar'
    }),
    expected: path.join( __dirname, 'expected/with-options' )
  }
]);

Run node test from the root of your plugin repo. gobble-test will take each test in turn, build the definition to gobble-test-result, and compare it with the contents of expected. If they differ, it will abort the run of tests, leaving gobble-test-result so that you can inspect it and figure out what went wrong.

License

MIT