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 🙏

© 2024 – Pkg Stats / Ryan Hefner

es6-pkg

v0.0.9

Published

Boilerplate for developing node modules using es6

Downloads

5

Readme

es6-pkg

Boilerplate for developing node modules using es6

Usage

npm i -g es6-pkg

mkdir your_project

cd your_project

# create `package.json`
npm init

# create files
es6pkg

npm install

# test the sample code
gulp

# coding

# check coverage
npm test

# commit your code and bump version

gulp build

cd build

npm publish

project directory

Put all your scripts in lib/, and tests in test/.

If there is a bin directory, you should modify gulpfile.babel.js.

⌘ tree .
.
├── gulpfile.babel.js
├── index.js
├── lib
│   └── main.es6
├── package.json
└── test
    └── main.es6

test and coverage

Run gulp or npm test, you will see something like:

test

Test

Refer to tape to learn how to write tests.

The default reporter is tap-spec.

NOTE: Tests should depend upon the same tape with gulp-tape, otherwise the reporter may fail to receive the output.

Coverage statistics is done by istanbul and isparta.

Lint

Refer to eslint to learn how to confiure.

Learn es6