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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@dhbradshaw/bh-shared

v1.1.1

Published

utilities for working with a list of objects

Readme

Minumum Viable ES6 NPM Package

Why create minimum viable es6 npm package repo?

A minimum viable npm es5 package is very simple -- just create a package.json with a name and a version in a folder and upload.

However, if you want to write in es6, then you probably want to still publish in es5. This adds a little complexity.

This package has a few parts put in place to make that work.

  1. The source files are placed in a src folder.
  2. .babelrc and package.json are set up so that a build command will populate the build folder.
  3. main is declared to be index.js in the build folder.
  4. tests are in the tests folder
  5. jest is added as a dev-dependancy and a test script is provided
  6. .gitignore avoids committing the generated es5 so that github isn't polluted with generated code.
  7. .npmignore avoids adding the source code so that npm isn't polluted with es6 code.

Cool. So what do I do to use it?

It's pretty easy. Here are the steps.

1. Clone this repo

$ git clone [email protected]:dhbradshaw/minimal-es6-npm-package.git

2. Customize package.json

You'll have to update the package name. You may will want to update at least some of several other fields: author, license, etc.
And of course you'll probably want to configure your dependencies and dev dependencies.

3. Add your code to src

Make sure that you export any part of your api that you want will available in the end product.

4. Add your tests to tests and run them

Make sure to run your tests before deploying your package.

Run babel to populate the build directory

yarn babel

or

npm run babel

Register with npm if necessary

You can register with npm by using the add user command if you're not already there:

$ npm adduser

Publish!

From the same directly as your package.json, run

npm publish

Resources:

https://docs.npmjs.com/getting-started/publishing-npm-packages

http://stackoverflow.com/questions/29738381/how-to-publish-a-module-written-in-es6-to-npm