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

browserify-patch-server

v0.4.2

Published

Patch server for browserify

Downloads

16

Readme

Browserify patch server

Because we need HMR an analog for webpack's webpack-dev-server

Requirements

node > 0.10 or io.js > 2.0 installed

Install

npm install browserify-patch-server --save-dev

Getting started

Start browserify-patch-server:

node_modules/.bin/bfps bundles/file.js

or

node_modules/.bin/browserify-patch-server bundles/file.js

With browserify-patch-server you can also track multiple bundles:

node_modules/.bin/browserify-patch-server bundles/file.js bundles/file2.js

Now you need to have a client which will connect to localhost:<port>. After establishing connection you'll start receiving messages:

  • Bundle has been changed successfully:
  {
    "bundle": BundleName <String>,
    "patch": Patch <String>
  }
  • Bundle has syntax error:
  {
    "bundle": BundleName <String>,
    "error": Error <String>
  }

Also, once your client will connect to the server it'll receive an initial bundle(s) and message that connection has been established:

{
  "message": "Connected to browserify-patch-server",
  "sources": sources <Array>,
}

Examples

Feel free to submit your example!

Configuration

By default, browserify-patch-server use port 8081 for websocket server. If you want to change this port you need to specify -p or --port parameter:

node_modules/.bin/browserify-patch-server bundles/file.js -p 8888