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

commodiquia

v1.2.2

Published

watch mode for browserify builds

Downloads

11

Readme

watchify

watch mode for browserify builds

Update any source file and your browserify bundle will be recompiled on the spot.

example

Use watchify with all the same arguments as browserify except that -o is mandatory:

$ watchify main.js -o static/bundle.js

Now as you update files, static/bundle.js will be automatically re-compiled on the fly.

You can use -v to get more verbose output to show when a file was written:

$ watchify browser.js -d -o static/bundle.js -v
610598 bytes written to static/bundle.js
610606 bytes written to static/bundle.js
610597 bytes written to static/bundle.js
610606 bytes written to static/bundle.js
610597 bytes written to static/bundle.js
610597 bytes written to static/bundle.js

usage

All the bundle options are the same as the browserify command except for -v.

methods

var watchify = require('watchify')

var w = watchify(opts)

Create a browserify bundle w from opts.

w is exactly like a browserify bundle except that caches file contents and emits an 'update' event when a file changes. You should call w.bundle() after the 'update' event fires to generate a new bundle. Calling w.bundle() extra times past the first time will be much faster due to caching.

events

w.on('update', function (ids) {})

When the bundle changes, emit the array of bundle ids that changed.

install

With npm do:

$ npm install -g watchify

to get the watchify command and:

$ npm install watchify

to get just the library.

license

MIT