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

29 lines
526 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/cli to 9.0.0-next.8 (#32980) The payload size increase in the ES5 bundles is (at least partially) expected, due to fixing some down-leveling corner cases. Related CLI issue: angular/angular-cli#15673 PR Close #32980
2019-10-04 07:03:58 -04:00
"runtime-es2015": 2987,
build(docs-infra): update @angular/material to 10.0.1 (#37898) This commit updates the version of Angular Components used in angular.io to version 10.0.1. It also updates the angular.io app to adapt to breaking changes. PR Close #37898
2020-07-07 07:13:37 -04:00
"main-es2015": 450880,
build(docs-infra): update @angular/cli to 10.0.0-next.3 (#36145) Update the Angular CLI and Angular framework packages to latest `@next` versions. Also, update the app to look more closely to how a newly generated app with the latest CLI would look like. PR Close #36145
2020-05-05 08:28:48 -04:00
"polyfills-es2015": 52685
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/cli to 9.0.0-next.8 (#32980) The payload size increase in the ES5 bundles is (at least partially) expected, due to fixing some down-leveling corner cases. Related CLI issue: angular/angular-cli#15673 PR Close #32980
2019-10-04 07:03:58 -04:00
"runtime-es2015": 2987,
fix(core): Allow modification of lifecycle hooks any time before bootstrap (#35464) Currently we read lifecycle hooks eagerly during `ɵɵdefineComponent`. The result is that it is not possible to do any sort of meta-programing such as mixins or adding lifecycle hooks using custom decorators since any such code executes after `ɵɵdefineComponent` has extracted the lifecycle hooks from the prototype. Additionally the behavior is inconsistent between AOT and JIT mode. In JIT mode overriding lifecycle hooks is possible because the whole `ɵɵdefineComponent` is placed in getter which is executed lazily. This is because JIT mode must compile a template which can be specified as `templateURL` and those we are waiting for its resolution. - `+` `ɵɵdefineComponent` becomes smaller as it no longer needs to copy lifecycle hooks from prototype to `ComponentDef` - `-` `ɵɵNgOnChangesFeature` feature is now always included with the codebase as it is no longer tree shakable. Previously we have read lifecycle hooks from prototype in the `ɵɵdefineComponent` so that lifecycle hook access would be monomorphic. This decision was made before we had `T*` data structures. By not reading the lifecycle hooks we are moving the megamorhic read form `ɵɵdefineComponent` to instructions. However, the reads happen on `firstTemplatePass` only and are subsequently cached in the `T*` data structures. The result is that the overall performance should be same (or slightly better as the intermediate `ComponentDef` has been removed.) - [ ] Remove `ɵɵNgOnChangesFeature` from compiler. (It will no longer be a feature.) - [ ] Discuss the future of `Features` as they hinder meta-programing. Fix #30497 PR Close #35464
2020-02-14 21:02:11 -05:00
"main-es2015": 450301,
build: update to typescript 3.9.5 (#37456) This TypeScript version contains the revert for the classes wrapped in IIFE change that was introduced in version 3.9. PR Close #37456
2020-06-05 06:46:47 -04:00
"polyfills-es2015": 52630
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/cli to 9.0.0-next.8 (#32980) The payload size increase in the ES5 bundles is (at least partially) expected, due to fixing some down-leveling corner cases. Related CLI issue: angular/angular-cli#15673 PR Close #32980
2019-10-04 07:03:58 -04:00
"runtime-es2015": 3097,
ci: decrease expected AIO and integration payload sizes (#36578) (#36578) The changes in #36687 removed enough code to exceed the CI check limits, so the expected main-es2015 size needs adjusting. PR Close #36578
2020-05-21 02:40:11 -04:00
"main-es2015": 429200,
refactor: disable sanitization for [style] and [style.prop] bindings (#35621) This patch is the first of many commits to disable sanitization for [stlye.prop] and [style] bindings in Angular. Historically, style-based sanitization has only been required for old IE browsers (IE6 and IE7). Since Angular does not support these old browsers at all, there is no reason for the framework to support style-based sanitization. PR Close #35621
2020-02-21 17:11:00 -05:00
"polyfills-es2015": 52195
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(core): Allow modification of lifecycle hooks any time before bootstrap (#35464) Currently we read lifecycle hooks eagerly during `ɵɵdefineComponent`. The result is that it is not possible to do any sort of meta-programing such as mixins or adding lifecycle hooks using custom decorators since any such code executes after `ɵɵdefineComponent` has extracted the lifecycle hooks from the prototype. Additionally the behavior is inconsistent between AOT and JIT mode. In JIT mode overriding lifecycle hooks is possible because the whole `ɵɵdefineComponent` is placed in getter which is executed lazily. This is because JIT mode must compile a template which can be specified as `templateURL` and those we are waiting for its resolution. - `+` `ɵɵdefineComponent` becomes smaller as it no longer needs to copy lifecycle hooks from prototype to `ComponentDef` - `-` `ɵɵNgOnChangesFeature` feature is now always included with the codebase as it is no longer tree shakable. Previously we have read lifecycle hooks from prototype in the `ɵɵdefineComponent` so that lifecycle hook access would be monomorphic. This decision was made before we had `T*` data structures. By not reading the lifecycle hooks we are moving the megamorhic read form `ɵɵdefineComponent` to instructions. However, the reads happen on `firstTemplatePass` only and are subsequently cached in the `T*` data structures. The result is that the overall performance should be same (or slightly better as the intermediate `ComponentDef` has been removed.) - [ ] Remove `ɵɵNgOnChangesFeature` from compiler. (It will no longer be a feature.) - [ ] Discuss the future of `Features` as they hinder meta-programing. Fix #30497 PR Close #35464
2020-02-14 21:02:11 -05:00
}