angular-cn/goldens/size-tracking/aio-payloads.json

{
  "aio": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 453213,
        "polyfills-es2015": 52685
      }
    }
  },
  "aio-local": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 2987,
        "main-es2015": 451406,
        "polyfills-es2015": 52630
      }
    }
  },
  "aio-local-viewengine": {
    "master": {
      "uncompressed": {
        "runtime-es2015": 3097,
        "main-es2015": 429710,
        "polyfills-es2015": 52195
      }
    }
  }
}
ci: Update 1% payload size test (#20524) PR Close #20524 2017-11-18 12:26:33 -08: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 12:47:04 +02: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 14:03:58 +03:00			`"runtime-es2015": 2987,`
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 12:46:47 +02:00			`"main-es2015": 453213,`
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 15:28:48 +03: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 12:47:04 +02: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 13:01:37 +03: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 14:03:58 +03:00			`"runtime-es2015": 2987,`
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 12:46:47 +02:00			`"main-es2015": 451406,`
			`"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 13:01:37 +03: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-10-01 00:54:00 +03: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 13:01:37 +03: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 14:03:58 +03:00			`"runtime-es2015": 3097,`
fix(core): disable tsickle pass when producing APF packages (#37221) As of TypeScript 3.9, the tsc emit is not compatible with Closure Compiler due to https://github.com/microsoft/TypeScript/pull/32011. There is some hope that this will be fixed by a solution like the one proposed in https://github.com/microsoft/TypeScript/issues/38374 but currently it's unclear if / when that will happen. Since the Closure support has been somewhat already broken, and the tsickle pass has been a source of headaches for some time for Angular packages, we are removing it for now while we rethink our strategy to make Angular Closure compatible outside of Google. This change has no effect on our Closure compatibility within Google which work well because all the code is compiled from sources and passed through tsickle. This change only disables the tsickle pass but doesn't remove it. A follow up PR should either remove all the traces of tscikle or re-enable the fixed version. BREAKING CHANGE: Angular npm packages no longer contain jsdoc comments to support Closure Compiler's advanced optimizations The support for Closure compiler in Angular packages has been experimental and broken for quite some time. As of TS3.9 Closure is unusable with the JavaScript emit. Please follow https://github.com/microsoft/TypeScript/issues/38374 for more information and updates. If you used Closure compiler with Angular in the past, you will likely be better off consuming Angular packages built from sources directly rather than consuming the version we publish on npm which is primarily optimized for Webpack/Rollup + Terser build pipeline. As a temporary workaround you might consider using your current build pipeline with Closure flag `--compilation_level=SIMPLE`. This flag will ensure that your build pipeline produces buildable and runnable artifacts, at the cost of increased payload size due to advanced optimizations being disabled. If you were affected by this change, please help us understand your needs by leaving a comment on https://github.com/angular/angular/issues/37234. PR Close #37221 2020-05-19 18:11:37 -07:00			`"main-es2015": 429710,`
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 14:11:00 -08: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 13:01:37 +03: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 12:47:04 +02:00			`}`
ci: increase AIO payload size limit (#35538) This commit updates AIO payload size limit that is triggering a problem after merging https://github.com/angular/angular/commit/f95b8ce07e71cf0b736cec1f617349a44e41f939. That commit added some payload size, but all checks were "green" for the PR (https://github.com/angular/angular/pull/34481) after rebase that happened a couple hours before the merge, so this is an accumulated payload size increase from multiple changes. The goal of this commit is to bring the master and patch branches back to "green" state. PR Close #35538 2020-02-18 17:52:34 -08:00			`}`