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

generator-nm-es6

v2.0.0

Published

Develop node modules in ES6 using babel

Downloads

2

Readme

generator-nm-es6

Yeoman generator for developing your own node modules in ES6.

Installation and usage

  • Install previous dependencies if you haven't already (npm install -g yo mocha).
  • Install the generator (npm install -g generator-nm-es6)
  • Run the generator (yo nm-es6)

Development Workflow

the folder tree structure after running the generator and running npm run build will look something like this:

.  
├── .gitignore  
├── .jshintrc  
├── .travis.yml  
├── README.md   
├── dist  
│   └── index.js  
├── package.json  
├── source  
│   └── index.js  
└── test  
    └── index.spec.js
  • Everything inside the source and test folder can be written in ES6. It will be automatically be transpiled and put into a temporary "build" directory.
  • Source maps are in-built, which means that any error in the code will be reported as an error in the original code, and not as an error in the transpiled code.
  • All the tests reside inside the test folder and will be run using mocha.

npm scripts

  • npm test - Run all tests and jshint. Also watches files for changes.
  • npm run test:cover - Run tests and generate code coverage information.
  • npm run build - Transpiles ES6 into build folder. Should be run before publishing the node module.

source

The source folder is where all the source code files go. The index.js file inside this folder will be the entry point to the node module, i.e. the node module will export whatever source/index.js exports.

test

The test folder contains all the tests for the source files. Tests are run using mocha.

dist

This is the actual folder the node module is run from once it is packaged and published. The index.js file here is the actual entry point of the node module. The dist folder exactly mimics the contents of the source folder, or the build/source folder.

Publishing your node module

  • Run npm run build
  • Commit and push your code.
  • Follow the instructions here

License

MIT © sohamkamani