This is a browserify development server inspired by beefy and wzrd, but with a stronger focus on incremental bundling, LiveReload (including CSS injection), and other experimental features down the road.
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. Examples:
#run watchify on port 9966budo index.js#run watchify with explicit output filebudo index.js --outfile bundle.js --verbose#run watchify with some options and trigger LiveReload on changebudo index.js --live --transform brfs
You can open
localhost:9966 to see the content in action.
budo index.js -o bundle.js | garnish
See docs for more features.
PRs/suggestions/comments welcome. Props to @caspervonb for the early groundwork.
- basic usage
- error reporting
- running tests and examples
- script injection with budo-chrome
- programmatic usage (Gulp, Grunt)
- rapid prototyping with budō and wzrd
budo command-line interface. Other options like
--transform are sent to browserify/watchify.
Usage:budo [entries] [opts]Options:--outfile, -o path to output bundle--port the port to run, default 9966--host the host, default "localhost"--dir the directory to serve, and the base
By default, the
--debug option will be sent to watchify (for source maps). If this is unwanted, you can use
--debug=false to disable source maps.
--outfile is relative to the specified
The API mirrors the CLI except you must provide a
stream for logging, and it does not attempt to auto-portfind.
var budo =
See API usage for more details.
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ō.
MIT, see LICENSE.md for details.