Repository navigation
Comparing changes
Open a pull request
base repository: angular/angular
base: 19.2.12
head repository: angular/angular
compare: 19.2.13
- 13 commits
- 90 files changed
- 7 contributors
Commits on May 21, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 2f5912e - Browse repository at this point
Copy the full SHA 2f5912eView commit details
Commits on May 22, 2025
-
fix(zone.js): classes that extend Error should retain cause property (#…
Configuration menu - View commit details
-
Copy full SHA for 5f1bd07 - Browse repository at this point
Copy the full SHA 5f1bd07View commit details -
fix(service-worker): do not register service worker if app is destroy…
Configuration menu - View commit details
-
Copy full SHA for b15bddf - Browse repository at this point
Copy the full SHA b15bddfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0a51f36 - Browse repository at this point
Copy the full SHA 0a51f36View commit details -
refactor: ensure tsurge migrations have clear ownership of files (#61421
) (#61612) Currently there can be cases, exlusively in 3P, where multiple tsconfig projects have overlap of source files. This is the default setup of new CLI applications as well. When this is the case, Tsurge will treat each tsconfig as an isolated compilation unit (given the concepts and mental model to support scalable batching). This is wrong though, and the same `.ts` source file can appear in two migration invocations; resulting in duplicate replacements or analysis (depending on the migration). We've worked around this problem in the past by deduplicating replacements, or migrating to an ID-based approach with natural deduplication. This worked, but it's just working around the root cause. This commit attempts to fix the root cause by adjusting Tsurge to ensure that no source file ever appears in two compilation units. This is naively achieved by not adding a source file to a migration unit, if it was part of a previous one. This is expected to be fine given the nature of Tsurge migrations that are built to operate on isolated pieces anyway— so it shouldn't be problematic if e.g. `app.component.ts` ends up being part of the test tsconfig compilation unit (we avoid this order though by visiting build targets first). PR Close #61421 PR Close #61612
Configuration menu - View commit details
-
Copy full SHA for 1a811c9 - Browse repository at this point
Copy the full SHA 1a811c9View commit details -
refactor: clean-up deduplication workaround from migrations (#61421) (#…
Configuration menu - View commit details
-
Copy full SHA for c101a3a - Browse repository at this point
Copy the full SHA c101a3aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2ae69f7 - Browse repository at this point
Copy the full SHA 2ae69f7View commit details -
build: migrate localize package to use rules_js (#61615)
Use ts_project to build localize package PR Close #61615
Configuration menu - View commit details
-
Copy full SHA for d4d4be8 - Browse repository at this point
Copy the full SHA d4d4be8View commit details -
Configuration menu - View commit details
-
Copy full SHA for e38cc41 - Browse repository at this point
Copy the full SHA e38cc41View commit details -
build: migrate platform-browser and platform-browser-dynamic package …
Configuration menu - View commit details
-
Copy full SHA for 2a26944 - Browse repository at this point
Copy the full SHA 2a26944View commit details -
build: migrate platform-server to rules_js (#61619)
Migrate platform-server to use ts_project and ng_project. PR Close #61619
Configuration menu - View commit details
-
Copy full SHA for a6d5479 - Browse repository at this point
Copy the full SHA a6d5479View commit details
Commits on May 23, 2025
-
1
Configuration menu - View commit details
-
Copy full SHA for 2c876b4 - Browse repository at this point
Copy the full SHA 2c876b4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 517cde4 - Browse repository at this point
Copy the full SHA 517cde4View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 19.2.12...19.2.13