Skip to content
Permalink

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: 14.2.7
Choose a base ref
...
head repository: angular/angular-cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 14.2.11
Choose a head ref
  • 17 commits
  • 20 files changed
  • 5 contributors

Commits on Nov 2, 2022

  1. fix(@schematics/angular): guard schematics should include all guards …

    …(CanMatch)
    
    The `CanMatch` guard was added in v14.1 but not added
    to the list of possible interfaces to implement.
    This commit adds `CanMatch` to the list of possible
    interfaces to implement. It has the same type imports
    as the CanLoad interface.
    
    (cherry picked from commit f837f6d)
    atscott authored and dgp1130 committed Nov 2, 2022
    Configuration menu
    Copy the full SHA
    4b0ee8a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    4f730aa View commit details
    Browse the repository at this point in the history

Commits on Nov 7, 2022

  1. fix(@angular-devkit/build-angular): isolate zone.js usage when render…

    …ing server bundles
    
    When generating an app-shell via the app-shell builder, the server application rendering
    will now take place within a Node.js Worker. Since the rendering requires the presence of
    Zone.js, this change allows for the Zone.js patching to be isolated from the remainder
    of the builder and Angular CLI code. This prevents Zone.js from persisting past the needed
    render operation. This also allows for a workaround to a Zone.js/Node.js v18 problem where
    the TypeScript dynamic import workaround involving the Function constructor to ensure a native
    dynamic import expression will cause a failure when running on Node.js v18.10.
    
    (cherry picked from commit 484cda5)
    alan-agius4 committed Nov 7, 2022
    Configuration menu
    Copy the full SHA
    12b2dc5 View commit details
    Browse the repository at this point in the history

Commits on Nov 8, 2022

  1. fix(@angular-devkit/architect): default to failure if no builder resu…

    …lt is provided
    
    Currently, if an architect builder does not provide any results, the CLI will crash
    trying to access an error message property on the result. Instead architect will now
    provide a default failure result `{ success: false }` in the event that the builder
    exits prior to generating a result. Thrown errors continue to be propagated as before.
    
    (cherry picked from commit 774e83d)
    clydin authored and alan-agius4 committed Nov 8, 2022
    Configuration menu
    Copy the full SHA
    e3e7877 View commit details
    Browse the repository at this point in the history

Commits on Nov 9, 2022

  1. Configuration menu
    Copy the full SHA
    ac3d230 View commit details
    Browse the repository at this point in the history

Commits on Nov 11, 2022

  1. fix(@angular/cli): respect registry in RC when running update through…

    … yarn
    
    This commit fixes an issue where when `ng update` was ran using `yarn` (`yarn ng update`) the registry was always being overridden to `https://registry.yarnpkg.com`.
    
    This is because yarn will set the `npm_config_registry` env variable to `https://registry.yarnpkg.com` even when an RC file is present with a different repository.
    
    (cherry picked from commit 0dcb199)
    alan-agius4 committed Nov 11, 2022
    Configuration menu
    Copy the full SHA
    7541e04 View commit details
    Browse the repository at this point in the history

Commits on Nov 16, 2022

  1. fix(@angular-devkit/build-angular): update loader-utils to 3.2.1

    `loader-utils` is vulnerable to Regular Expression Denial of Service (ReDoS) via url variable.
    
    See: GHSA-3rfm-jhwj-7488
    
    Closes #24241
    alan-agius4 authored and dgp1130 committed Nov 16, 2022
    Configuration menu
    Copy the full SHA
    21cea0b View commit details
    Browse the repository at this point in the history
  2. test(@angular/cli): update NPM range in npm-7 test

    With the previous range NPM 9 was being installed which is not compatible with the version of node that Angular version 13 supports.
    alan-agius4 authored and dgp1130 committed Nov 16, 2022
    Configuration menu
    Copy the full SHA
    87277d9 View commit details
    Browse the repository at this point in the history
  3. test(@angular/cli): remove node:assert usage.

    `node:assert` is not available in Node.js version 14.15.5
    alan-agius4 authored and dgp1130 committed Nov 16, 2022
    Configuration menu
    Copy the full SHA
    f1fe0ea View commit details
    Browse the repository at this point in the history

Commits on Nov 17, 2022

  1. fix(@angular/cli): exclude @angular/material@7.x from ng add packag…

    …e discovery
    
    `@angular/material@7.x` uses unbounded ranges for its framework peer dependencies.
    This can cause `ng add` to pick these versions of the package if the newer versions
    are not compatible since the peer dependency ranges would match any newer stable
    framework version.
    
    (cherry picked from commit 9260087)
    (cherry picked from commit 1a58436)
    clydin authored and dgp1130 committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    6446091 View commit details
    Browse the repository at this point in the history
  2. fix(@angular/cli): exclude @angular/localize@<10.0.0 from ng add pa… (

    #24152)
    
    * fix(@angular/cli): exclude `@angular/localize@<10.0.0` from ng add package discovery
    
    `@angular/localize@<10.0.0` has no peer dependencies. This can cause `ng add` to pick these versions of the package if the newer versions.
    
    See: https://app.circleci.com/pipelines/github/angular/angular-cli/27402/workflows/faa64532-541a-4bea-b599-3c53afe42019/jobs/364822
    ```
    Test Process error Error: Process exit error - "ng add @angular/localize --skip-confirmation": 1...
    
    STDOUT:
    
    STDERR:
    npm version 7.4.0 detected. When using npm 7 with the Angular CLI, npm version 7.5.6 or higher is recommended.
    - Determining package manager...
    ℹ Using package manager: npm
    - Searching for compatible package version...
    ✔ Found compatible package version: @angular/localize@10.0.0-next.7.
    - Loading package information from registry...
    ✔ Package information loaded.
    - Installing packages...
    ✔ Packages successfully installed.
    NOT SUPPORTED: keyword "id", use "$id" for schema ID
    ```
    
    * fixup! fix(@angular/cli): exclude `@angular/localize@<10.0.0` from ng add package discovery
    
    Co-authored-by: Charles <19598772+clydin@users.noreply.github.com>
    
    Co-authored-by: Charles <19598772+clydin@users.noreply.github.com>
    (cherry picked from commit 65a0983)
    (cherry picked from commit 35e5f42)
    2 people authored and dgp1130 committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    9ce386c View commit details
    Browse the repository at this point in the history
  3. test(@angular/cli): fix version specifier test

    Remove `ng add @angular/localize@latest` test. This is currently failing as `@angular/localize@latest` does not support Node.js version 14.15
    alan-agius4 authored and dgp1130 committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    9dcea09 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    e9d30d4 View commit details
    Browse the repository at this point in the history

Commits on Mar 15, 2023

  1. Configuration menu
    Copy the full SHA
    6df825d View commit details
    Browse the repository at this point in the history

Commits on Mar 16, 2023

  1. Configuration menu
    Copy the full SHA
    ddd33bf View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    d177918 View commit details
    Browse the repository at this point in the history
Loading