Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

budo

Package Overview
Dependencies
Maintainers
1
Versions
126
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

budo

a browserify server for rapid prototyping

  • 3.1.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8.7K
decreased by-4.08%
Maintainers
1
Weekly downloads
 
Created
Source

budō

stable

This is a browserify development server inspired by beefy and wzrd, but specifically focused on incremental reloading and LiveReload integration (including CSS injection).

Note that budo needs a copy of watchify installed. It can be either local (preferred) or global.

npm install budo watchify -g

The simplest use cases will start up a server with a default index.html and incrementally bundle your source on filesave. The requests are delayed until the bundle has finished, so you won't be served stale or empty bundles if you refresh the page mid-update. Examples:

# serve file on port 9966
budo index.js

# enable LiveReload on html/css/js changes
# show timing information on re-bundle
budo index.js --verbose --live

# pass some options to browserify
budo index.js --live -- -t babelify --full-paths

Then open http://localhost:9966 to see the content in action.

To pretty-print in terminal, garnish, bistre or another ndjson-based stream can be used:

budo index.js | garnish

See docs for more features. PRs/suggestions/comments welcome.

docs

usage

NPM

CLI

Details for budo command-line interface. Other options will be sent to browserify.

Usage:
  budo [entries] [opts]

Options:
  --help, -h       show help message
  --port           the port to run, default 9966
  --host           the host, default "localhost"
  --dir            the directory to serve, and the base for --outfile
  --serve          override the bundle path being served
  --live           enable LiveReload integration
  --live-plugin    enable LiveReload but do not inject script tag
  --live-port      the LiveReload port, default 35729
  --verbose, -v    verbose timing information for re-bundles
  --poll=N         use polling for file watch, with optional interval N
  --no-stream      do not print messages to stdout
  --no-debug       do not use inline source maps

By default, messages will be printed to stdout and debug will be sent to browserify (for source maps). You can turn these off with --no-stream and --no-debug, respectively.

Any options after -- will be sent unchanged to browserify. This is currently required for subarg syntax. Example:

budo index.js --live -- -t [ babelify --exetensions .es6 ]

API

The API mirrors the CLI except it does not write to process.stdout by default, and does not attempt to find available ports from a base port.

var budo = require('budo')

budo('./src/index.js', {
  live: true,             //live reload
  stream: process.stdout, //log to stdout
  port: 8000              //use this port
}).on('connnect', function(ev) {
  //...
})

See API usage for more details.

Script Injection

screenshot

(click for demo)

The original motivation for making budō was to build a simple tool around Chrome Script Injection. This has since split off into its own repository: budo-chrome to minimize the scope of budō.

License

MIT, see LICENSE.md for details.

Keywords

FAQs

Package last updated on 20 Apr 2015

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc