angular/packages/core/schematics/migrations.json

{
  "schematics": {
    "block-template-entities": {
      "version": "17.0.0",
      "description": "Angular v17 introduces a new control flow syntax that uses the @ and } characters. This migration replaces the existing usages with their corresponding HTML entities.",
      "factory": "./migrations/block-template-entities/bundle"
    },
    "migration-v17-compiler-options": {
      "version": "17.0.0",
      "description": "CompilerOption.useJit and CompilerOption.missingTranslation are unused under Ivy. This migration removes their usage",
      "factory": "./migrations/compiler-options/bundle"
    },
    "migration-transfer-state": {
      "version": "17.0.0",
      "description": "Updates `TransferState`, `makeStateKey`, `StateKey` imports from `@angular/platform-browser` to `@angular/core`.",
      "factory": "./migrations/transfer-state/bundle"
    },
    "invalid-two-way-bindings": {
      "version": "17.3.0",
      "description": "Updates two-way bindings that have an invalid expression to use the longform expression instead.",
      "factory": "./migrations/invalid-two-way-bindings/bundle"
    }
  }
}
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983 2019-02-27 19:30:38 +00:00			`{`
			`"schematics": {`
refactor(migrations): rename migration to remove version prefix (#51926) The version prefix in the migration name is redundant. PR Close #51926 2023-09-27 12:21:30 +00:00			`"block-template-entities": {`
refactor(migrations): remove unused version 16 migrations (#51926) When updating to version 17, version 16 migrations cannot be executed thus making them redundant to have in the package. PR Close #51926 2023-09-27 12:19:31 +00:00			`"version": "17.0.0",`
feat(core): add schematic to escape block syntax characters (#51905) #51891 introduces a new syntax that assigns a new meaning to the `@` and `}` in Angular templates. This is problematic for existing apps which may have the characters in their templates already, because it can lead to syntax errors. These changes add an `ng update` schematic that will replace any usages of the special characters with their HTML entities. PR Close #51905 2023-09-26 19:41:43 +00:00			`"description": "Angular v17 introduces a new control flow syntax that uses the @ and } characters. This migration replaces the existing usages with their corresponding HTML entities.",`
			`"factory": "./migrations/block-template-entities/bundle"`
feat(migrations): schematic to remove deprecated CompilerOptions properties (#49672) `useJit` and `missingTranslation` have been deprecated since v13 and are unused in Ivy. They can be safely removed. PR Close #49672 2023-04-02 19:01:47 +00:00			`},`
			`"migration-v17-compiler-options": {`
			`"version": "17.0.0",`
			`"description": "CompilerOption.useJit and CompilerOption.missingTranslation are unused under Ivy. This migration removes their usage",`
			`"factory": "./migrations/compiler-options/bundle"`
feat(migrations): Schematics for `TransferState`, `StateKey` and `makeStateKey` migration. (#49594) These 3 classes have been moved from platform-browser to core by #49563 PR Close #49594 2023-03-24 17:04:47 +00:00			`},`
			`"migration-transfer-state": {`
			`"version": "17.0.0",`
			"description": "Updates `TransferState`, `makeStateKey`, `StateKey` imports from `@angular/platform-browser` to `@angular/core`.",
			`"factory": "./migrations/transfer-state/bundle"`
feat(core): add migration for invalid two-way bindings (#54630) As a part of #54154, an old parser behavior came up where two-way bindings were parsed by appending `= $event` to the event side. This was problematic, because it allowed some non-writable expressions to be passed into two-way bindings. These changes introduce a migration that will change the two-way bindings into two separate input/output bindings that represent the old behavior so that in a future version we can throw a parser error for the invalid expressions. ```ts // Before @Component({ template: `<input [(ngModel)]="a && b"/>` }) export class MyComp {} // After @Component({ template: `<input [ngModel]="a && b" (ngModelChange)="a && (b = $event)"/>` }) export class MyComp {} ``` PR Close #54630 2024-02-28 13:45:09 +00:00			`},`
			`"invalid-two-way-bindings": {`
			`"version": "17.3.0",`
			`"description": "Updates two-way bindings that have an invalid expression to use the longform expression instead.",`
			`"factory": "./migrations/invalid-two-way-bindings/bundle"`
feat(core): update schematic to migrate to explicit query timing (#28983) Introduces an update schematic for the "@angular/core" package that automatically migrates pre-V8 "ViewChild" and "ContentChild" queries to the new explicit timing syntax. This is not required yet, but with Ivy, queries will be "dynamic" by default. Therefore specifying an explicit query timing ensures that developers can smoothly migrate to Ivy (once it's the default). Read more about the explicit timing API here: https://github.com/angular/angular/pull/28810 PR Close #28983 2019-02-27 19:30:38 +00:00			`}`
			`}`
refactor(migrations): remove migrations from previous versions (#49603) These migration can no longer be executed by the users, thus we remove them. PR Close #49603 2023-03-27 12:42:19 +00:00			`}`