angular-cn/aio/scripts/_payload-limits.json

{
  "aio": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 455897,
        "polyfills-es2015": 52195
      }
    }
  },
  "aio-local": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 448928,
        "polyfills-es2015": 52195
      }
    }
  },
  "aio-local-viewengine": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 3097,
        "main-es2015": 426513,
        "polyfills-es2015": 52195
      }
    }
  }
}
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 aio to @angular/cli@9.0.0-rc.11 (#35043) PR Close #35043 2020-01-29 15:33:02 -05:00			`"main-es2015": 455897,`
			`"polyfills-es2015": 52195`
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,`
feat(ivy): Change static priority resolution to be same level as directive it belongs to (#34938) This change changes the priority order of static styling. Current priority: ``` (least priority) - Static - Component - Directives - Template - Dynamic Binding - Component - Map/Interpolation - Property - Directives - Map/Interpolation - Property - Template - Map/Interpolation - Property (highest priority) ``` The issue with the above priority is this use case: ``` <div style="color: red;" directive-which-sets-color-blue> ``` In the above case the directive will win and the resulting color will be `blue`. However a small change of adding interpolation to the example like so. (Style interpolation is coming in https://github.com/angular/angular/pull/34202) ``` <div style="color: red; width: {{exp}}px" directive-which-sets-color-blue> ``` Changes the priority from static binding to interpolated binding which means now the resulting color is `red`. It is very surprising that adding an unrelated interpolation and style can change the `color` which was not changed. To fix that we need to make sure that the static values are associated with priority of the source (directive or template) where they were declared. The new resulting priority is: ``` (least priority) - Component - Static - Map/Interpolation - Property - Directives - Static - Map/Interpolation - Property - Template - Static - Map/Interpolation - Property (highest priority) ``` PR Close #34938 2020-01-26 15:29:03 -05:00			`"main-es2015": 448928,`
build(docs-infra): update aio to @angular/cli@9.0.0-rc.11 (#35043) PR Close #35043 2020-01-29 15:33:02 -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			`}`
			`}`
			`},`
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,`
build(docs-infra): update aio to @angular/cli@9.0.0-rc.11 (#35043) PR Close #35043 2020-01-29 15:33:02 -05:00			`"main-es2015": 426513,`
			`"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			`}`
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			`}`