b6dfc8b08c
The `payload-size.sh` script is mainly used on CI to calculate, check and potentially save (on non-PR builds) the sizes of the bundles for various apps (including angular.io). If everything goes well (i.e. the checks pass, meaning that the sizes did not increase above the specified threshold) nothing is shown in the CI logs. In some cases, it is useful to be able to see what the sizes were in a specific build; e.g. for debugging purposes or when investigating a gradual increase that happened over time. (Some of this info is available on https://size.angular.io/, but not all.) Previously, the only way to find out what the sizes were for a specific build was to checkout the corresponding commit locally and build the target app, which in turn requires building all Angular packages and can take some time. Given that the sizes are already calculated on CI, this was a waste. This commit makes it easy to find out the bundle sizes for a specific build/commit by always printing out the calculated sizes (thus making them show up in the CI logs). PR Close #33099 |
||
|---|---|---|
| .circleci | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| aio | ||
| docs | ||
| integration | ||
| modules | ||
| packages | ||
| scripts | ||
| third_party | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .nvmrc | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| WORKSPACE | ||
| browser-providers.conf.js | ||
| gulpfile.js | ||
| karma-js.conf.js | ||
| package.json | ||
| protractor-perf.conf.js | ||
| renovate.json | ||
| shims_for_IE.js | ||
| test-events.js | ||
| test-main.js | ||
| tslint.json | ||
| yarn.lock | ||
| yarn.lock.readme.md | ||
README.md
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.