npm install budo -g
Running budo will start 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 9966budo index.js# enable LiveReload on html/css/js changes# show timing information on re-bundlebudo index.js --verbose --live# pass some options to browserifybudo index.js --live -- -t babelify --full-paths
Then open http://localhost:9966 to see the content in action.
# install garnish if you don't have itnpm install garnish -g# pipe to garnish for pretty-printingbudo index.js | garnish
See docs for more features. PRs/suggestions/comments welcome.
- basic usage
- API and integrations (Gulp, Grunt, npm scripts)
- error reporting
- running tests and examples
- script injection with budo-chrome
- rapid prototyping with budō and wzrd
budo command-line interface. Other options (like
-t) 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
By default, messages will be printed to
--debug will be sent to browserify (for source maps). You can turn these off with
-- is passed directly to browserify; this is currently needed for subarg syntax. Example:
budo indexjs --live -- -t babelify --exetensions es6
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 =
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.