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

@twilson63/wzrd

v1.2.2

Published

Super minimal browserify development server. Inspired by [beefy](http://npmjs.org/beefy) but with less magic

Downloads

5

Readme

wzrd

Super minimal browserify development server. Inspired by beefy but with less magic

Build Status

installation

npm install wzrd -g

note that you must have a copy of browserify installed as well. It can be either local (preferred) or global.

npm install browserify --save

usage

wzrd app.js

This will start a local development server (default of localhost:9966) that serves all files in the current folder with the exception of app.js, which will be browserified instead. wzrd will spawn the command browserify app.js and send the output bundle back to the client.

If no index.html is present in the directory you run wzrd in, one will be generated for you that has a <script src='app.js'></script> in it.

mappings

You can also specify a mapping:

wzrd app.js:bundle.js

This means if a request to the server comes in for bundle.js, wzrd will run the command browserify app.js and serve that.

multiple entries

wzrd app.js:bundle.js foo.js:bar.js baz.js

https

wzrd app.js --https

this will start a local https server (by default https://localhost:4443) and generate a self signed SSL certificate. You will get a certificate error in your browser, but if you ignore the error the app should load.

passing extra args to browserify

wzrd app.js -- -t brfs

anything after -- will get passed directly to browserify as arguments. so the example above would spawn the command browserify app.js -t brfs

pushstate server support

wzrd app.js --pushstate

if you want to leverage the html5 pushstate and support natural urls in your frontend application you can use the --pushstate flag. This flag will instruct the wzrd server to always return index.html for any file not found request from your server.