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

bde

v1.4.0

Published

Browserify Development Environment

Downloads

54

Readme

bde

Browserify Development Environment.

If you are developing on your local machine using browserify, then bde is your friend (though you should also definitely check out budo).

NPM

bitHound Score

Running

In a directory that you are building a browserify module in, simply run bde. This will start bde on port 8080 and watch for any files ending in bundle.js.

If you want to start it on a particular port, then specify the port as the first command-line argument (e.g. bde 8090) or using the -p flag (e.g. bde -p 8090).

If you would like to watch for a different suffix, use the -s flag (e.g. bde -s foo.js).

Conventions

bde will serve pretty much any file, courtesy of ecstatic. When particular files are requested, however, they will be routed through browserify:

  • *-bundle.js (look for the filename prefixed by -bundle.js and run through browserify)

Using HTTPS

If you wish to run a bde server using HTTPS then you simply need to push relevant server.crt, server.key and server.ca (if required) files into the working directory from which you start your application. If detected bde will start the server on using HTTPS instead of HTTP.

Using Browserify Transform

The best way to configure custom browserify behaviour is to use the browserify package.json configuration options. Previous versions of bde tried to use overcomplicated logic to identify transforms that were available, until I accidentally worked out it wasn't required :smile:

License(s)

MIT

Copyright (c) 2017 Damon Oehlman [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.