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

wa-build

v0.0.33

Published

1. node-js is installed 2. npm is installed 3. Grunt CLI is installed `npm install -g grunt-cli`

Downloads

4

Readme

Prerequisites

  1. node-js is installed
  2. npm is installed
  3. Grunt CLI is installed npm install -g grunt-cli

Using wa-build

Prior to creating your own project, to install the version of wa-build from this source tree, run npm install . -g from the root of this project. This may be preferred if the newest version is not available in an npm repository.

  1. mkdir foo - Create a directory for your component.
  2. cd foo - CD to your component directory.
  3. npm init - Initialize your component.
  4. npm install --save-dev wa-build - Install wa-build.
  5. npm install --save-dev grunt - Install local grunt.
  6. npm install --save-dev babel-runtime - Install ES6 support.
  7. cp node_modules/wa-build/templates/gruntfile.js . - Copy the gruntfile template to your component.
  8. cp node_modules/wa-build/templates/.npmignore . - Copy the .npmignore template to your component so dist/ files will be published to npm.
  9. grunt init - Run one-time build prerequisites.
  10. mkdir src - Create a src directory for your source code.
  11. touch src/index.js - Create src/index.js that will export your component.
  12. grunt - Test the build.

The resulting compiled files are available at

  • dist/index.js - ES6 to ES5 transpiled. Used for imports from other packages.
  • lib/foo.js - Browserified, human readable. Use for debugging in web browsers.
  • lib/foo.min.js - Optimized, obfuscated. Not human readable. Use for production in web browsers.

grunt dev

To continue building upon changing source code, run grunt dev after a successful grunt build. Files will be served up at http://localhost:9001.

You must run grunt before running grunt watch!