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

beerxml

v1.0.6

Published

Making Beer Import XML

Downloads

8

Readme

ES6 library starter

Version Build Status Code style: airbnb

A boilerplate for a universal (Node, web, UMD) ES6 library.

Quick usage

  1. Clone this repo.
  2. Change all relevant entries in package.json and README.md, so they match your new shiny library.
  3. Run npm install to install dev dependencies.
  4. Write your ES6 code in src folder.
  5. Write your ES6 tests in test folder.
  6. Run npm run build to build for node. This will compile to ES5, minify, and output the result to lib folder.
  7. Run npm run build-web to build and pack the files for the web. This will output the result to dist folder.
  8. Run npm publish to pulish to the world.

(Or, if you don't need Webpack bundling, you can use the even lighter ES6 starter).

Detailed overview

Installation

After cloning this repository, make sure to change all the relevant entries in package.json so they match your library.

npm install

Build for npm

npm run build

This will:

  1. Run Webpack starting from the entry point file (src/library.js, can be configured)
  2. Convert all files in src folder from ES6 to ES5
  3. According to the bundle-node flag in package.json, it will either:
  4. Leave them as separate files, or -
  5. Minify and bundle them using Webpack, without their node_modules dependencies
  6. Output the result to the lib folder

Build for web

npm run build-web

This will:

  1. Run Webpack starting from the entry point file (src/library.js, can be configured)
  2. Convert all files from ES6 to ES5
  3. Minify them, including all of their module dependencies, as a UMD module (so the file will be self-contained)
  4. Output the file to the dist folder

Test

npm run test

Configuration

In package.json, change all the relevant entries so they match your library. Under the section library, you can configure:

  1. Library name (defaults to "Library")
  2. Webpack entry point (defaults to library.js)
  3. Dist folder for Node (defaults to lib)
  4. Dist folder for Web (defaults to dist)
  5. Choose whether to bundle for Node (defaults to true)

License

MIT