-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: angular/angular-cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 19.0.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: angular/angular-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 19.0.4
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 18 files changed
- 4 contributors
Commits on Dec 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ed30cfb - Browse repository at this point
Copy the full SHA ed30cfbView commit details -
docs(@angular/ssr): remove duplicate
@return
commentRemove duplicate `@return` tsdoc comment. (cherry picked from commit 1ca260e)
Configuration menu - View commit details
-
Copy full SHA for 4a5c5e4 - Browse repository at this point
Copy the full SHA 4a5c5e4View commit details -
fix(@angular-devkit/build-angular): handle windows spec collisions
(cherry picked from commit 9e2d3fb)
Configuration menu - View commit details
-
Copy full SHA for 23667ed - Browse repository at this point
Copy the full SHA 23667edView commit details -
perf(@angular/build): reuse TS package.json cache when rebuilding
TypeScript 5.6 and higher added functionality that will search for a `package.json` file for source files that are part of the program (e.g., `.d.ts`) and within a node modules directory. This can be an expensive tasks especially considering the large amount of `.d.ts` files within packages. TypeScript supports using a cache of known `package.json` files to improve the performance of this task. The Angular CLI will now provide and reuse this cache across rebuilds during watch mode. This includes the use of `ng serve`. The performance difference is most apparent for the Angular template diagnostic step of the build. Internally the Angular compiler creates a new template typechecking program which causes the `package.json` search process to occur. By leveraging the cache, this process becomes a series of cache hits. In the event that files are modified within the node modules directory, the cache is invalidated and the following rebuild may be longer as a result. (cherry picked from commit 75998eb)
Configuration menu - View commit details
-
Copy full SHA for 14451e2 - Browse repository at this point
Copy the full SHA 14451e2View commit details -
fix(@angular/build): show error when Node.js built-ins are used durin…
…g `ng serve` This commit ensures consistent behavior between `ng build` and `ng serve`. Previously, `ng serve` did not display an error message when Node.js built-in modules were included in browser bundles. By default, Vite replaces Node.js built-ins with empty modules, which can lead to unexpected runtime issues. This update addresses the problem by surfacing clear error messages, providing better developer feedback and alignment between the two commands. Closes: #27425 (cherry picked from commit 06f478b)
Configuration menu - View commit details
-
Copy full SHA for fc41f50 - Browse repository at this point
Copy the full SHA fc41f50View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6cfbb88 - Browse repository at this point
Copy the full SHA 6cfbb88View commit details
Loading
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.0.3...19.0.4