angular-docs-cn/integration/_payload-limits.json
Matias Niemelä 7cc4225eb9 fix(ivy): ensure binding ordering doesn't mess up when a NO_CHANGE value is encountered (#32143)
Prior to this fix if a `NO_CHANGE` value was assigned to a binding, or
an interpolation value rendererd a `NO_CHANGE` value, then the presence
of that value would cause the internal counter index values to not
increment properly. This patch ensures that this doesn't happen and
that the counter/bitmask values update accordingly.

PR Close #32143
2019-09-04 11:54:19 -07:00

47 lines
958 B
JSON

{
"cli-hello-world": {
"master": {
"uncompressed": {
"runtime": 1497,
"main": 157021,
"polyfills": 45399
}
}
},
"cli-hello-world-ivy-minimal": {
"master": {
"uncompressed": {
"runtime": 1440,
"main": 13264,
"polyfills": 45340
}
}
},
"cli-hello-world-ivy-compat": {
"master": {
"uncompressed": {
"runtime": 1440,
"main": 123904,
"polyfills": 45340
}
}
},
"cli-hello-world-ivy-i18n": {
"master": {
"uncompressed": {
"runtime": 1440,
"main": 141209,
"polyfills": 45949
}
}
},
"hello_world__closure": {
"master": {
"uncompressed": {
"bundle": "TODO(i): temporarily increase the payload size limit from 105779 - this is due to a closure issue related to ESM reexports that still needs to be investigated",
"bundle": 177137
}
}
}
}