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

{
  "aio": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 456581,
        "polyfills-es2015": 52487
      }
    }
  },
  "aio-local": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 448956,
        "polyfills-es2015": 52487
      }
    }
  },
  "aio-local-viewengine": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 3097,
        "main-es2015": 427017,
        "polyfills-es2015": 52487
      }
    }
  }
}
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 to @angular/material 9.0.0-rc.8 (#34966) This update increases the main bundle by ~0.6KB payload size snapshot: 456581 Jan 24 22:07 dist/main-es2015.38c39f92eab2fcc8c835.js 541321 Jan 24 22:06 dist/main-es5.38c39f92eab2fcc8c835.js 52487 Jan 24 22:05 dist/polyfills-es2015.b374ef3555a700a97add.js 146193 Jan 24 22:05 dist/polyfills-es5.c7dc569e6c646e42fade.js 2987 Jan 24 22:05 dist/runtime-es2015.29be4028399ae41ba25e.js 2981 Jan 24 22:05 dist/runtime-es5.29be4028399ae41ba25e.js PR Close #34966 2020-01-25 01:23:22 -05:00			`"main-es2015": 456581,`
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			`"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,`
fix(ivy): ensure `DebugNode`/`DebugElement` are tree-shakeable in Ivy (#35003) There are different `DebugNode`/`DebugElement` implementations (and associated helper functions) for ViewEngine and Ivy. Additionally, these classes/functions, which are defined inside the `core` package, are imported by the `platform-browser` package. Previously, this code was not tree-shaken as expected in Ivy. #30130 partially addressed the issue, but only for the case where `core` and `platform-browser` end up in the same closure after webpack's scope hoisting. In cases where this is not the case, our webpack/terser based tooling is not capable of tree-shaking it. This commit fixes the problem, by ensuring that the code retained in Ivy mode (due to the cross-package import) does not unnecessarily reference `DebugNode`/`DebugElement`, allowing the code to be tree-shaken away. This results in a 7.6KB reduction in the size of the main angular.io bundle. Jira issue: [FW-1802](https://angular-team.atlassian.net/browse/FW-1802) PR Close #35003 2020-01-28 04:13:23 -05:00			`"main-es2015": 448956,`
ci(docs-infra): update payload size limits (#35003) PR Close #35003 2020-01-28 08:05:57 -05:00			`"polyfills-es2015": 52487`
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,`
fix(ivy): ensure `DebugNode`/`DebugElement` are tree-shakeable in Ivy (#35003) There are different `DebugNode`/`DebugElement` implementations (and associated helper functions) for ViewEngine and Ivy. Additionally, these classes/functions, which are defined inside the `core` package, are imported by the `platform-browser` package. Previously, this code was not tree-shaken as expected in Ivy. #30130 partially addressed the issue, but only for the case where `core` and `platform-browser` end up in the same closure after webpack's scope hoisting. In cases where this is not the case, our webpack/terser based tooling is not capable of tree-shaking it. This commit fixes the problem, by ensuring that the code retained in Ivy mode (due to the cross-package import) does not unnecessarily reference `DebugNode`/`DebugElement`, allowing the code to be tree-shaken away. This results in a 7.6KB reduction in the size of the main angular.io bundle. Jira issue: [FW-1802](https://angular-team.atlassian.net/browse/FW-1802) PR Close #35003 2020-01-28 04:13:23 -05:00			`"main-es2015": 427017,`
ci(docs-infra): update payload size limits (#35003) PR Close #35003 2020-01-28 08:05:57 -05:00			`"polyfills-es2015": 52487`
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			`}`