Track Dart bundle size

[kegluneq]

See #5294 for pointers

[IgorMinar]

• we should replicate the internal hello world project
• run that in a separate travis job
• add analytics
• consider implementing (in a follow up PR) a mechanism that would compare the current payload size with current master size and fail the build if more than X%. this will require storing the master payload size somewhere which complicates the matters. maybe we could use firebase for this?

[yjbanov]

+1 on @IgorMinar's proposals. I think it's reasonable to cap incremental increases. We still need the absolute <100kb gzipped and <300kb minified caps, as that's our SLA for internal customers, and also without them no matter what incremental percentage we choose it is still exponential.

[mark1010]

#5311 Duplicate Output may be related. I see the same issue in the js build, and some level of duplication in the generated js, which may be impacting code size.

[ochafik]

Note: no need to store the build size anywhere, you could just checkout the master branch (or the previous commit if $TRAVIS_BRANCH == "master"), then just build all the playground examples, find the outputs and print their gzipped size into some json, do this once again for the branch's version and compare with a tiny node.js script (all this in a separate travis env).

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}