iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/goldens/size-tracking/aio-payloads.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/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3033,
fix(docs-infra): print info to help debugging SW cache issue (#41106) From time to time, an angular.io page fails to load due to requesting a file that cannot be found neither on the server nor in the cache. We believe this is caused by the browser's partially clearing a cache. See #28114 for more details. Some time ago, we introduced [SwUpdate#unrecoverable][1] to help work around this issue by [reloading the page][2] when such an error is detected. However, this issue still pops up occasionally (for example, #41073). In an attempt to help diagnose the issue, this commit prints more info regarding the SW state and cache content when this error occurs. It will result in something like the following being printed to the console: ``` ServiceWorker: activated Cache: ngsw:/:db:control (2 entries) - https://angular.io/assignments: {"f5f02035-ee1f-463c-946c-e8b85badca25":"5c95f89a85255a6fefb4045a20f751ef32b2f3a4"} - https://angular.io/latest: {"latest":"5c95f89a85255a6fefb4045a20f751ef32b2f3a4"} Cache: ngsw:/:5c95f89a85255a6fefb4045a20f751ef32b2f3a4:assets:app-shell:cache (24 entries) - https://angular.io/0-es2015.867022f8bb092ae1efb1.worker.js - https://angular.io/announcement-bar-announcement-bar-module-es2015.1b5b762c9c8837c770f8.js - https://angular.io/api-api-list-module-es2015.40a43cd22f50f64d63bb.js ... Cache: ngsw:/:db:ngsw:/:5c95f89a85255a6fefb4045a20f751ef32b2f3a4:assets:app-shell:meta (1 entries) - https://angular.io/https://fonts.gstatic.com/s/robotomono/v13/L0x5DF4xlVMF-BfR8bXMIjhLq3-cXbKD.woff2: {"ts":1615031956601,"used":true} If you see this error, please report an issue at https://github.com/angular/angular/issues/new?template=3-docs-bug.md including the above logs. ``` NOTE: This change increases the main bundle by 1649B (0.37%), but it can be reverted as soon as we gather enough info to diagnose the issue. [1]: https://angular.io/api/service-worker/SwUpdate#unrecoverable [2]: https://github.com/angular/angular/blob/c676ec1ce5d586d4bc46/aio/src/app/sw-updates/sw-updates.service.ts#L55-L61 PR Close #41106
2021-03-06 09:30:42 -05:00
"main-es2015": 450953,
fix(docs-infra): avoid unnecessarily loading Custom Elements ES5 shim (#41162) The custom elements spec is not compatible with ES5 style classes. This means ES2015 code compiled to ES5 will not work with a native implementation of Custom Elements. To support browsers that natively support Custom Elements but not ES2015 modules, we load `@webcomponents/custom-elements/src/native-shim.js`, which minimally augments the native implementation to be compatible with ES5 code. (See [here][1] for more details.) Previously, the shim was included in `polyfills.ts`, which meant it was loaded in all browsers (even those supporting ES2015 modules and thus not needing the shim). This commit moves the shim from `polyfills.ts` to a `nomodule` script tag in `index.html`. This will ensure that it is only loaded in browsers that do not support ES2015 modules and thus do not needed the shim. NOTE: This commit also reduces size of the polyfills bundle by ~400B (52609B --> 52215B). [1]: https://www.npmjs.com/package/@webcomponents/custom-elements#es5-vs-es2015 PR Close #41162
2021-03-10 14:53:25 -05:00
"polyfills-es2015": 52215
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/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3033,
refactor(core): remove the need for `ɵɵinjectPipeChangeDetectorRef()` (#41231) This instruction was created to work around a problem with injecting a `ChangeDetectorRef` into a pipe. See #31438. This fix required special metadata for when the thing being injected was a `ChangeDetectorRef`. Now this is handled by adding a flag `InjectorFlags.ForPipe` to the `ɵɵdirectiveInject()` call, which avoids the need to special test_cases `ChangeDetectorRef` in the generated code. PR Close #41231
2021-03-19 03:18:33 -04:00
"main-es2015": 451600,
"polyfills-es2015": 52215
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/* and @angular/cli to 11.0.0-rc.2 (#39600) This commit updates `@angular/*` and `@angular/cli` (and related packages) to version 11.0.0-rc.2. Apart from the automatic migrations, this commit also tries to align `aio/` with new apps generated by the latest CLI. (See [here][1] for a diff between a v10.1.3 and a v11.0.0-rc.2 CLI app.) [1]: https://github.com/cexbrayat/angular-cli-diff/compare/10.1.3...11.0.0-rc.2 PR Close #39600
2020-11-18 05:36:06 -05:00
"runtime-es2015": 3153,
fix(platform-browser): configure `XhrFactory` to use `BrowserXhr` (#41313) With this change we move `XhrFactory` to the root entrypoint of `@angular/commmon`, this is needed so that we can configure `XhrFactory` DI token at a platform level, and not add a dependency between `@angular/platform-browser` and `@angular/common/http`. Currently, when using `HttpClientModule` in a child module on the server, `ReferenceError: XMLHttpRequest is not defined` is being thrown because the child module has its own Injector and causes `XhrFactory` provider to be configured to use `BrowserXhr`. Therefore, we should configure the `XhrFactory` at a platform level similar to other Browser specific providers. BREAKING CHANGE: `XhrFactory` has been moved from `@angular/common/http` to `@angular/common`. **Before** ```ts import {XhrFactory} from '@angular/common/http'; ``` **After** ```ts import {XhrFactory} from '@angular/common'; ``` Closes #41311 PR Close #41313
2021-03-23 05:28:54 -04:00
"main-es2015": 437306,
feat(compiler-cli): introduce HttpContext request context (#25751) A long-requested feature for HttpClient is the ability to store and retrieve custom metadata for requests, especially in interceptors. This commit implements this functionality via a new context object for requests. Each outgoing HttpRequest now has an associated "context", an instance of the HttpContext class. An HttpContext can be provided when making a request, or if not then an empty context is created for the new request. This context shares its lifecycle with the entire request, even across operations that change the identity of the HttpRequest instance such as RxJS retries. The HttpContext functions as an expando. Users can create typed tokens as instances of HttpContextToken, and read/write a value for the key from any HttpContext object. This commit implements the HttpContext functionality. A followup commit will add angular.io documentation. PR Close #25751
2021-03-09 15:20:48 -05:00
"polyfills-es2015": 52493
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
}
refactor(core): remove the need for `ɵɵinjectPipeChangeDetectorRef()` (#41231) This instruction was created to work around a problem with injecting a `ChangeDetectorRef` into a pipe. See #31438. This fix required special metadata for when the thing being injected was a `ChangeDetectorRef`. Now this is handled by adding a flag `InjectorFlags.ForPipe` to the `ɵɵdirectiveInject()` call, which avoids the need to special test_cases `ChangeDetectorRef` in the generated code. PR Close #41231
2021-03-19 03:18:33 -04:00
}