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-module-starter

v2.0.0

Published

Starter kit to create npm modules using ES6 and Babel with sensible defaults

Downloads

8

Readme

es6-module-starter

npm version travis build information Coverage Status

Starter kit to create npm modules using ES6 and Babel with sensible defaults.

Why use this?

Want to create an npm module with ES6? Don't want to wait for full node support? Don't want to mess around with creating all those directories and setting up babel and npm scripts? Then this is for you.

How to get started

  1. Install node and npm.
  2. Clone this repo: git clone https://github.com/vinniegarcia/es6-module-starter.git my-module-name
  3. Install dependencies: npm i
  4. Start hacking like it's 2015!

Modules used/included

  • babel - compiles ES6 source to ES5. The --experimental flag is also enabled so you can use ES7 features.
  • tape and argg for simple, effective testing with less magic than mocha or jasmine.
  • Istanbul to report test coverage.
  • eslint and babel-eslint to analyze your code for stylistic issues.
  • plato to analyze the complexity of your source code.
  • coveralls to send your test results to coveralls.io.

These are just defaults. Feel free to swap out eslint for jshint, or tape for mocha, or whatever you use for CI instead of coveralls.

Layout

  • src/ - Your ES6 source code goes here. Files have a .es6 extension for syntax highlighting in Sublime Text with babel-sublime
  • src/tests/ - Your ES6 tests go here.
  • src/.eslintrc - ESLint configuration
  • coverage/ - Code coverage reports are output here.
  • dist/ - Your generated ES5 source is output here. This directory is under gitignore.
  • .gitignore - a sensible .gitignore file to prevent you from checking in generated source.
  • .npmignore - preconfigured to publish only the generated source code.
  • package.json - Customize this to publish your own module.
  • .travis.yml - Customize this if you use Travis CI for builds.
  • .coveralls.yml - Customize this if you use coveralls for code coverage.
  • README.md - Delete all this and write your own.

npm scripts

These scripts are the main way to interact with your module as you develop it.

  • compile - run babel to compile your ES6 source to ES5. Output goes to the dist/ directory.
  • lint - run ESLint on your ES6 source and reports any style errors.
  • tape - test your code.
  • coverage - run Istanbul on your code to report coverage. Reports output in HTML to the coverage/istanbul directory.
  • istanbul - run Istanbul, but output only lcov files for coveralls to read.
  • coveralls - run coveralls, using Istanbul's lcov report as input.
  • plato - run plato, a code analysis tool, on your generated source (plato doesn't support ES6 at the moment; as soon as it does I'll swap it to analyze ES6 source).
  • test - run tape, Istanbul, and coveralls.
  • prepublish - compiles your ES6 source to prepare for publishing to npm.

Questions?

File an issue and I'll try to answer you.