14.2.11 (2023年03月16日)

@angular-devkit/build-angular

Special Thanks

Alan Agius and Joey Perrott

13.3.11 (2023年03月16日)

@angular-devkit/build-angular

Special Thanks

Alan Agius and Joey Perrott

16.0.0-next.4 (2023年03月15日)

@angular-devkit/build-angular

Special Thanks

Alan Agius, Charles Lyding and Paul Gschwendtner

15.2.3 (2023年03月15日)

@angular-devkit/build-angular

Special Thanks

Alan Agius and Paul Gschwendtner

16.0.0-next.3 (2023年03月08日)

@angular-devkit/schematics-cli

@angular/cli

@angular-devkit/build-angular

Special Thanks

Alan Agius, Charles Lyding and Kristiyan Kostadinov

15.2.2 (2023年03月08日)

@angular-devkit/schematics-cli

@angular-devkit/build-angular

Special Thanks

Alan Agius

16.0.0-next.2 (2023年03月01日)

Breaking Changes

@angular-devkit/build-angular

• Deprecated outputPath and outputPaths from the server and browser builder have been removed from the builder output. Use outputs instead.

  Note: this change does not effect application developers.

@angular-devkit/build-angular

Special Thanks

Alan Agius, Doug Parker and Paul Gschwendtner

15.2.1 (2023年03月01日)

@angular-devkit/build-angular

Special Thanks

Alan Agius and Paul Gschwendtner

16.0.0-next.1 (2023年02月23日)

@angular-devkit/build-angular

Special Thanks

Alan Agius

16.0.0-next.0 (2023年02月22日)

Breaking Changes

@angular/cli

• The deprecated defaultCollection workspace option has been removed. Use schematicCollections instead.

  Before

  "defaultCollection": "@angular/material"

  After

  "schematicCollections": ["@angular/material"]

• The deprecated defaultProject workspace option has been removed. The project to use will be determined from the current working directory.

• Node.js v14 support has been removed

  Node.js v14 is planned to be End-of-Life on 2023年04月30日. Angular will stop supporting Node.js v14 in Angular v16.
  Angular v16 will continue to officially support Node.js versions v16 and v18.

@schematics/angular

• ng g resolver and ng g guard now generate a functional resolver or guard by default. It is still possible to generate a (deprecated) class-based resolver or guard by using ng g resolver --no-functional or ng g guard --no-functional.
• The CLI no longer allows to generate CanLoad guards. Use CanMatch instead.

@angular-devkit/core

• Several changes to the SchemaRegistry.
  • compile method now returns a Promise.
  • Deprecated flatten has been removed without replacement.
• • ContentHasMutatedException, InvalidUpdateRecordException, UnimplementedException and MergeConflictException API from @angular-devkit/core have been removed in favor of the API from @angular-devkit/schematics.
  • UnsupportedPlatformException - A custom error exception should be created instead.

@angular-devkit/schematics

• The depracated UpdateBuffer has been removed and UpdateBuffer2
  is renamed to UpdateBuffer. With this change the related and
  deprecated symbols ContentCannotBeRemovedException and Chunk
  have also been removed.

@ngtools/webpack

• NGCC integration has been removed and as a result Angular View Engine libraries will no longer work.

@schematics/angular

@angular/cli

@angular-devkit/core

@angular-devkit/schematics

@ngtools/webpack

Special Thanks

Alan Agius, Charles Lyding, Cédric Exbrayat, Doug Parker and Lukas Spirig