| 1 | Usage: browserify [entry files] {OPTIONS}
|
| 2 |
|
| 3 | Standard Options:
|
| 4 |
|
| 5 | --outfile, -o Write the browserify bundle to this file.
|
| 6 | If unspecified, browserify prints to stdout.
|
| 7 |
|
| 8 | --require, -r A module name or file to bundle.require()
|
| 9 | Optionally use a colon separator to set the target.
|
| 10 |
|
| 11 | --entry, -e An entry point of your app
|
| 12 |
|
| 13 | --ignore, -i Replace a file with an empty stub. Files can be globs.
|
| 14 |
|
| 15 | --exclude, -u Omit a file from the output bundle. Files can be globs.
|
| 16 |
|
| 17 | --external, -x Reference a file from another bundle. Files can be globs.
|
| 18 |
|
| 19 | --transform, -t Use a transform module on top-level files.
|
| 20 |
|
| 21 | --command, -c Use a transform command on top-level files.
|
| 22 |
|
| 23 | --standalone -s Generate a UMD bundle for the supplied export name.
|
| 24 | This bundle works with other module systems and sets the name
|
| 25 | given as a window global if no module system is found.
|
| 26 |
|
| 27 | --debug -d Enable source maps that allow you to debug your files
|
| 28 | separately.
|
| 29 |
|
| 30 | --help, -h Show this message
|
| 31 |
|
| 32 | For advanced options, type `browserify --help advanced`.
|
| 33 |
|
| 34 | Specify a parameter.
|