honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/goldens/size-tracking/aio-payloads.json

30 lines
527 B
JSON
Raw Normal View History

ci: Update 1% payload size test (#20524) PR Close #20524
2017-11-18 15:26:33 -05:00
{
ci: fix the payload-size checking scripts (#20683) The scripts were accidentally broken in #20524. More specifically, when a limit was exceeded the script would break while trying to log an error message due to a missing `commit` variable. This commit fixes it and also does some minor clean-up (improve docs, use more descriptive variable names, remove dead code, etc). PR Close #20683
2017-11-29 05:47:04 -05:00
"aio": {
"master": {
"uncompressed": {
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3033,
fix(docs-infra): support recovering from unrecoverable SW states (#39651) Occasionally, the SW would end up in a broken state where some of the eagerly cached resources of an older version were available in the local cache, but others (such as lazy-loaded bundles) were not. This would leave the app in a broken state and a blank screen would be displayed. See #28114 for a more detailed discussion. This commit takes advantage of the newly introduced (in v11) [SwUpdate#unrecoverable][1] API to detect these bad states and recover by doing a full page reload whenever an [UnrecoverableStateEvent][2] is emitted. Partially addresses #28114. NOTE: Currently, `SwUpdate.unrecoverable` only works if the app has already bootstrapped; i.e. if only lazy-loaded bundles have been purged from the cache. That should be fine in practice, since the cache entries are removed in least-recently-used order. Thus the eagerly loaded bundles will be the last to be removed from the cache (which rarely happens in practice). [1]: https://v11.angular.io/api/service-worker/SwUpdate#unrecoverable [2]: https://v11.angular.io/api/service-worker/UnrecoverableStateEvent PR Close #39651
2020-11-12 10:43:51 -05:00
"main-es2015": 447766,
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"polyfills-es2015": 52343
ci: fix the payload-size checking scripts (#20683) The scripts were accidentally broken in #20524. More specifically, when a limit was exceeded the script would break while trying to log an error message due to a missing `commit` variable. This commit fixes it and also does some minor clean-up (improve docs, use more descriptive variable names, remove dead code, etc). PR Close #20683
2017-11-29 05:47:04 -05:00
}
}
ci(docs-infra): check and track payload sizes for `test_aio_local` and `test_aio_local_ivy` (#31047) PR Close #31047
2019-06-14 06:01:37 -04:00
},
"aio-local": {
"master": {
"uncompressed": {
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3033,
fix(docs-infra): support recovering from unrecoverable SW states (#39651) Occasionally, the SW would end up in a broken state where some of the eagerly cached resources of an older version were available in the local cache, but others (such as lazy-loaded bundles) were not. This would leave the app in a broken state and a blank screen would be displayed. See #28114 for a more detailed discussion. This commit takes advantage of the newly introduced (in v11) [SwUpdate#unrecoverable][1] API to detect these bad states and recover by doing a full page reload whenever an [UnrecoverableStateEvent][2] is emitted. Partially addresses #28114. NOTE: Currently, `SwUpdate.unrecoverable` only works if the app has already bootstrapped; i.e. if only lazy-loaded bundles have been purged from the cache. That should be fine in practice, since the cache entries are removed in least-recently-used order. Thus the eagerly loaded bundles will be the last to be removed from the cache (which rarely happens in practice). [1]: https://v11.angular.io/api/service-worker/SwUpdate#unrecoverable [2]: https://v11.angular.io/api/service-worker/UnrecoverableStateEvent PR Close #39651
2020-11-12 10:43:51 -05:00
"main-es2015": 447975,
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"polyfills-es2015": 52493
ci(docs-infra): check and track payload sizes for `test_aio_local` and `test_aio_local_ivy` (#31047) PR Close #31047
2019-06-14 06:01:37 -04:00
}
}
},
build(docs-infra): turn on Ivy (#32923) The angular.io project uses Angular and CLI v9, which by default turns on Ivy mode. However, since ec4381dd4, we explicitly opt out of Ivy. This commit removes the `enabledIvy: false` configuration, thus allowing the default behavior of having Ivy on. NOTE: This commit only changes the angular.io projects. The docs examples need to be updated separately (first to Angular and CLI v9 and then to Ivy). PR Close #32923
2019-09-30 17:54:00 -04:00
"aio-local-viewengine": {
ci(docs-infra): check and track payload sizes for `test_aio_local` and `test_aio_local_ivy` (#31047) PR Close #31047
2019-06-14 06:01:37 -04:00
"master": {
"uncompressed": {
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3153,
build(docs-infra): update @angular/material to 11.0.0 (#39600) This commit updates `@angular/cdk` and `@angular/material` to version 11.0.0. PR Close #39600
2020-11-18 12:14:49 -05:00
"main-es2015": 431696,
build(docs-infra): update @angular/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"polyfills-es2015": 52493
ci(docs-infra): check and track payload sizes for `test_aio_local` and `test_aio_local_ivy` (#31047) PR Close #31047
2019-06-14 06:01:37 -04:00
}
}
ci: fix the payload-size checking scripts (#20683) The scripts were accidentally broken in #20524. More specifically, when a limit was exceeded the script would break while trying to log an error message due to a missing `commit` variable. This commit fixes it and also does some minor clean-up (improve docs, use more descriptive variable names, remove dead code, etc). PR Close #20683
2017-11-29 05:47:04 -05:00
}
fix(common): ensure scrollRestoration is writable (#30630) Some specialised browsers that do not support scroll restoration (e.g. some web crawlers) do not allow `scrollRestoration` to be writable. We already sniff the browser to see if it has the `window.scrollTo` method, so now we also check whether `window.history.scrollRestoration` is writable too. Fixes #30629 PR Close #30630
2019-05-23 08:44:46 -04:00
}