4cf197998a
Previously, our incremental build system kept track of the changes between the current compilation and the previous one, and used its knowledge of inter-file dependencies to evaluate the impact of each change and emit the right set of output files. However, a problem arose if the compiler was not able to extract a dependency graph successfully. This typically happens if the input program contains errors. In this case the Angular analysis part of compilation is never executed. If a file changed in one of these failed builds, in the next build it appears unchanged. This means that the compiler "forgets" to emit it! To fix this problem, the compiler needs to know the set of changes made _since the last successful build_, not simply since the last invocation. This commit changes the incremental state system to much more explicitly pass information from the previous to the next compilation, and in the process to keep track of changes across multiple failed builds, until the program can be analyzed successfully and the results of those changes incorporated into the emit plan. Fixes #32214 PR Close #33971 |
||
---|---|---|
.circleci | ||
.devcontainer | ||
.github | ||
.vscode | ||
aio | ||
docs | ||
integration | ||
modules | ||
packages | ||
scripts | ||
third_party | ||
tools | ||
.bazelignore | ||
.bazelrc | ||
.clang-format | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.nvmrc | ||
BUILD.bazel | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md | ||
WORKSPACE | ||
browser-providers.conf.js | ||
gulpfile.js | ||
karma-js.conf.js | ||
package.json | ||
protractor-perf.conf.js | ||
renovate.json | ||
shims_for_IE.js | ||
test-events.js | ||
test-main.js | ||
tslint.json | ||
yarn.lock | ||
yarn.lock.readme.md |
README.md
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.