Sourced from @âangular/common's releases.
v19.0.0
19.0.0 (2024-11-19)
Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84
Breaking Changes
compiler
this.fooproperty reads no longer refer to template context variables. If you intended to read the template variable, do not usethis..core
Angular directives, components and pipes are now standalone by default.
- Specify
standalone: falsefor declarations that are currently declared in@NgModules.ng updatefor v19 will take care of this automatically.TypeScript versions less than 5.5 are no longer supported.
Timing changes for
effectAPI (in developer preview):
effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).
effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.
ExperimentalPendingTaskshas been renamed toPendingTasks.The
autoDetectfeature ofComponentFixturewill now attach the fixture to theApplicationRef. As a result, errors during automatic change detection of the fixture be reported to theErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.
createComponentwill now render default fallback with emptyprojectableNodes.
- When passing an empty array to
projectableNodesin thecreateComponentAPI, the default fallback content of theng-contentwill be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')as aprojectableNode.// The first ng-content will render the default fallback content if present createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });// To prevent projecting the default fallback content: createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
Errors that are thrown during
ApplicationRef.tickwill now be rethrown when usingTestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:
- Instead of waiting for automatic change detection to happen, trigger
... (truncated)
Sourced from @âangular/common's changelog.
19.0.0 (2024-11-19)
Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84
Breaking Changes
compiler
this.fooproperty reads no longer refer to template context variables. If you intended to read the template variable, do not usethis..core
Angular directives, components and pipes are now standalone by default.
- Specify
standalone: falsefor declarations that are currently declared in@NgModules.ng updatefor v19 will take care of this automatically.TypeScript versions less than 5.5 are no longer supported.
Timing changes for
effectAPI (in developer preview):
effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).
effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.
ExperimentalPendingTaskshas been renamed toPendingTasks.The
autoDetectfeature ofComponentFixturewill now attach the fixture to theApplicationRef. As a result, errors during automatic change detection of the fixture be reported to theErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.
createComponentwill now render default fallback with emptyprojectableNodes.
- When passing an empty array to
projectableNodesin thecreateComponentAPI, the default fallback content of theng-contentwill be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')as aprojectableNode.// The first ng-content will render the default fallback content if present createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });// To prevent projecting the default fallback content: createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });
Errors that are thrown during
ApplicationRef.tickwill now be rethrown when usingTestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:
- Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write
expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
... (truncated)
7dfb127 refactor: add @__PURE__ next to @pureOrBreakMyCode for improved bundler c...da9c0c5 refactor: cleanup initializers that use ctor params (#58349)24c6373 feat(common): add optional rounded transform support in cloudinary image load...4b9accd feat(http): promote withRequestsMadeViaParent to stable. (#58221)13c1306 feat(common): disable keyvalue sorting using null compareFn (#57487)09df589 refactor(core): Migrate all packages with the explicit-standalone-flag sche...08b4a8a docs: move JSDoc below constructor (#57187)a36744e docs: move JSDoc before functions (#58087)0eb1c5c docs(common): Minor typo in code example (#58085)84b6896 refactor(platform-server): Add an ssr benchmark setup. (#57647)