iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/aio/scripts/_payload-limits.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/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 fw to 9.0.0-rc.11 (#34966) payload size snapshot: 455991 Jan 24 21:55 dist/main-es2015.2bcbba5871038ad608cd.js 540529 Jan 24 21:55 dist/main-es5.2bcbba5871038ad608cd.js 52487 Jan 24 21:53 dist/polyfills-es2015.b374ef3555a700a97add.js 146193 Jan 24 21:53 dist/polyfills-es5.c7dc569e6c646e42fade.js 2987 Jan 24 21:53 dist/runtime-es2015.3f56366a23f559d1feff.js 2981 Jan 24 21:53 dist/runtime-es5.3f56366a23f559d1feff.js PR Close #34966
2020-01-25 00:59:41 -05:00
"main-es2015": 455991,
"polyfills-es2015": 52487
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,
refactor(ivy): change styling to use programmatic API on updates (#34804) Previously we would write to class/style as strings `element.className` and `element.style.cssText`. Turns out that approach is good for initial render but not good for updates. Updates using this approach are problematic because we have to check to see if there was an out of bound write to style and than perform reconciliation. This also requires the browser to bring up CSS parser which is expensive. Another problem with old approach is that we had to queue the DOM writes and flush them twice. Once on element advance instruction and once in `hostBindings`. The double flushing is expensive but it also means that a directive can observe that styles are not yet written (they are written after directive executes.) The new approach uses `element.classList.add/remove` and `element.style.setProperty/removeProperty` API for updates only (it continues to use `element.className` and `element.style.cssText` for initial render as it is cheaper.) The other change is that the styling changes are applied immediately (no queueing). This means that it is the instruction which computes priority. In some circumstances it may result in intermediate writes which are than overwritten with new value. (This should be rare) Overall this change deletes most of the previous code and replaces it with new simplified implement. The simplification results in code savings. PR Close #34804
2020-01-15 19:52:54 -05:00
"main-es2015": 455803,
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
"polyfills-es2015": 52503
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,
refactor(ivy): Switch styling to new reconcile algorithm (#34616) NOTE: This change must be reverted with previous deletes so that it code remains in build-able state. This change deletes old styling code and replaces it with a simplified styling algorithm. The mental model for the new algorithm is: - Create a linked list of styling bindings in the order of priority. All styling bindings ere executed in compiled order and than a linked list of bindings is created in priority order. - Flush the style bindings at the end of `advance()` instruction. This implies that there are two flush events. One at the end of template `advance` instruction in the template. Second one at the end of `hostBindings` `advance` instruction when processing host bindings (if any). - Each binding instructions effectively updates the string to represent the string at that location. Because most of the bindings are additive, this is a cheap strategy in most cases. In rare cases the strategy requires removing tokens from the styling up to this point. (We expect that to be rare case)S Because, the bindings are presorted in the order of priority, it is safe to resume the processing of the concatenated string from the last change binding. PR Close #34616
2019-12-17 18:40:37 -05:00
"main-es2015": 425216,
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
"polyfills-es2015": 52503
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
}
build(zone.js): update zone.js to 0.10.2 (#31975) Bundle size changed in both zone.js(legacy) and zone-evergreen.js - zone.js(legacy) package increased a little because the following feature and fixes. 1. #31699, handle MSPointer events PR 2. https://github.com/angular/zone.js/pull/1219 to add __zone_symbol__ customization support - zone-evergreen.js package decreased because 1. the MSPointer PR only for legacy 2. the Object.defineProperty patch is moved to legacy #31660 PR Close #31975
2019-08-02 20:58:31 -04:00
}