-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bundlesize status check #1209
Comments
Resolved in #1586 |
We currently don't have any way of monitoring bundle size per PR, so this isnt resolved. ATM we just creep up to the limit, and are forced to increase it. |
Will look into this, I was going to see if there was a way travis could comment on our PR with the bundle size, or add it as a status anyway. Would be so much easier to understand what PR affected the bundles |
@hindsc52 Cheers, |
As we no longer "require" travis this integration should live in our Jenkins pipeline. |
Following discussion with @hindsc52 we've decided to adapt our own bundle size analysis implementation and report it's result as a status on github: https://developer.github.com/v3/repos/statuses/#create-a-status We have found that the bundlesize plugin maintainers have chosen to not support checking of the total bundle size (siddharthkp/bundlesize#205 (comment)) but instead favour ongoing monitoring of individual chunk file sizes. We believe this would result in too many status checks in our case. As an open question how many status checks would we want?
Typical bundles output for context:
|
hmmm we do not want to report on the service bundles just yet as that would be a lot of data in the status check (40+ services) Maybe for now we send the main, vendor and max service bundle (i.e. just report of the largest service bundle)? |
Sounds good to me, I'll investigate doing this and see how it goes. |
Following discussion with @hindsc52 , we decided a status check that does not track changes over time is not helpful; the build failing for an increase already gives us what we need. Closing as agreed. |
Is your feature request related to a problem? Please describe.
As we develop while on live we should be very focused on not bloating our application by mistake.
Describe the solution you'd like
Add a bundlesize checker script such as https://github.com/siddharthkp/bundlesize and pass it a github token via Jenkins credentials.
OR we could add a
BUNDLESIZE_GITHUB_TOKEN
var to travis, as it has a simple integrationDescribe alternatives you've considered
Writing our own script 👎
The text was updated successfully, but these errors were encountered: