Basic Usage
$yarn run bundlewatch --max-size 100kb ./webpack-build/*.js
Result breakdown at: https://ja2r7.app.goo.gl/aDzEQjBVMXxrCgaa7
PASS ./webpack-build/app.js: 30.71KB < 100KB (gzip)
FAIL ./webpack-build/vendor.js: 198.6KB > 100KB (gzip)
BundleWatch FAIL
This will give you command line output. If you want BundleWatch to report build status on your pull requests, see below.
Adding Build Status:
BundleWatch can report its status on your GitHub Pull Requests.

Setup CI Auth Variables Needed by BundleWatch:
BUNDLEWATCH_GITHUB_TOKEN
You will need to give BundleWatch access to your GitHub Statuses, which can be done by heading to: https://service.bundlewatch.io/setup-github
This will give you your BUNDLEWATCH_GITHUB_TOKEN
. You will need to set this as an environment variable in CI.
Setup CI Variables Needed by BundleWatch:
The most efficient way to get this running is to ensure that some environment variables are available for BundleWatch to find.
CI_REPO_OWNER
github.com/facebook/reactCI_REPO_NAME
github.com/facebook/reactCI_COMMIT_SHA
CI_BRANCH
信息
If you're using, Travis, CircleCI, Wrecker or Drone these should all work out of the box.
Have a look at the source code to see which variables are automatically found: https://github.com/bundlewatch/bundlewatch/blob/master/src/app/config/getCIVars.js
Viewing the results breakdown
After setting up the above you will have BuildStatus on your Pull Requests. Clicking the details link on the reported status will show you a results file breakdown.
