this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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)
Commits
09df589 refactor(core): Migrate all packages with the explicit-standalone-flag sche...
84b6896 refactor(platform-server): Add an ssr benchmark setup. (#57647)
9dbe6fc refactor: update license text to point to angular.dev (#57901)
513a4fe refactor(core): replace usages of removeChild (#57203)
a7b973e docs(docs-infra): Use shiki for code highlighting (#57059)
176b26f docs: remove private symbol from docs (#56851)
0bd55a6 refactor(docs-infra): complete removal of aio directory (#56496)
01172b8 build: update Node.js to match Angular CLI engines (#56187)
fb35130 build: update to latest dev infra code (#56128)
024e9bf refactor(core): Ensure animations are flushed before running render hooks (#5...
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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)
Commits
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...
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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()
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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)
Commits
df210a4 refactor(core): mark linkedSignal as developer preview (#58684)
e6514b9 fix(migrations): do not migrate next calls in template if not an EventEmitter...
91a616f refactor(core): add REQUEST, RESPONSE_INIT and REQUEST_CONTEXT tokens (...
fa1b021 refactor(core): add performance feature flag for incremental hydration (#58658)
5fe57d4 fix(core): fixes issues with control flow and incremental hydration (#58644)
715caea refactor(migrations): typos in signal migration incompatibility reasons (#58636)
e26797b fix(migrations): replace removed NgModules in tests with their exports (#58627)
b84ed2b fix(migrations): include the output migration in the defaults of the signal m...
a5e7a02 refactor(core): moves incremental hydration codebase to better locations (#58...
560282a fix(compiler): control flow nodes with root at the end projected incorrectly ...
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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)
Commits
93c3f7a build: remove usages of useDefineForClassFields: false (#58297)
1f45338 Revert "fix(forms): fix FormRecord type inference (#50750)" (#58315)
79d9be3 Revert "feat(forms): add ability to clear a FormRecord (#50750)" (#58315)
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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)
Commits
c36a1c0 fix(platform-browser): correctly add external stylesheets to ShadowDOM compon...
917e99d docs(platform-browser): update usage notes for incremental hydration (#58339)
19edf2c feat(core): add syntactic sugar for initializers (#53152)
69fc5ae feat(core): Add incremental hydration public api (#58249)
this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..
core
Angular directives, components and pipes are now standalone by default.
Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.
TypeScript versions less than 5.5 are no longer supported.
Timing changes for effect API (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.
ExperimentalPendingTasks has been renamed to PendingTasks.
The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.
createComponent will now render default fallback with empty projectableNodes.
When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.
// 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.tick
will now be rethrown when using TestBed. 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
dependabot[bot]
commented
5 hours ago
Bumps the angular group with 16 updates in the /webapp directory:
15.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.1019.0.015.2.919.0.015.4.018.1.115.4.018.1.115.4.018.1.115.4.117.18.1215.2.1019.0.016.2.519.0.015.2.1019.0.0Updates
@angular/animationsfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/animations's releases.... (truncated)
Changelog
Sourced from
@angular/animations's changelog.... (truncated)
Commits
09df589refactor(core): Migrate all packages with theexplicit-standalone-flagsche...84b6896refactor(platform-server): Add an ssr benchmark setup. (#57647)9dbe6fcrefactor: update license text to point to angular.dev (#57901)513a4ferefactor(core): replace usages of removeChild (#57203)a7b973edocs(docs-infra): Use shiki for code highlighting (#57059)176b26fdocs: remove private symbol from docs (#56851)0bd55a6refactor(docs-infra): complete removal of aio directory (#56496)01172b8build: update Node.js to match Angular CLI engines (#56187)fb35130build: update to latest dev infra code (#56128)024e9bfrefactor(core): Ensure animations are flushed before running render hooks (#5...Updates
@angular/commonfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/common's releases.... (truncated)
Changelog
Sourced from
@angular/common's changelog.... (truncated)
Commits
7dfb127refactor: add@__PURE__next to@pureOrBreakMyCodefor improved bundler c...da9c0c5refactor: cleanup initializers that use ctor params (#58349)24c6373feat(common): add optional rounded transform support in cloudinary image load...4b9accdfeat(http): promotewithRequestsMadeViaParentto stable. (#58221)13c1306feat(common): disable keyvalue sorting using null compareFn (#57487)09df589refactor(core): Migrate all packages with theexplicit-standalone-flagsche...08b4a8adocs: move JSDoc below constructor (#57187)a36744edocs: move JSDoc before functions (#58087)0eb1c5cdocs(common): Minor typo in code example (#58085)84b6896refactor(platform-server): Add an ssr benchmark setup. (#57647)Updates
@angular/compilerfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/compiler's releases.... (truncated)
Changelog
Sourced from
@angular/compiler's changelog.... (truncated)
Commits
806a61bfix(compiler): fix multiline selectors (#58681)e5d3abbfix(compiler): resolve:host:host-context(.foo)(#58681)80f5695fix(compiler): transform chained pseudo-selectors (#58681)2be161dfix(compiler): fix:hostparsing in pseudo-selectors (#58681)560282afix(compiler): control flow nodes with root at the end projected incorrectly ...86d8f6brefactor(compiler): trigger hmr load on initialization (#58465)abd0da7refactor(compiler): remove unused field from output AST (#58444)b25121efix(compiler): avoid having to duplicate core environment (#58444)98804fdfix(compiler): add more specific matcher for hydrate never block (#58360)c79b62crefactor(core): remove the standalone feature (#58288)Updates
@angular/corefrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/core's releases.... (truncated)
Changelog
Sourced from
@angular/core's changelog.... (truncated)
Commits
df210a4refactor(core): mark linkedSignal as developer preview (#58684)e6514b9fix(migrations): do not migrate next calls in template if not an EventEmitter...91a616frefactor(core): addREQUEST,RESPONSE_INITandREQUEST_CONTEXTtokens (...fa1b021refactor(core): add performance feature flag for incremental hydration (#58658)5fe57d4fix(core): fixes issues with control flow and incremental hydration (#58644)715caearefactor(migrations): typos in signal migration incompatibility reasons (#58636)e26797bfix(migrations): replace removed NgModules in tests with their exports (#58627)b84ed2bfix(migrations): include the output migration in the defaults of the signal m...a5e7a02refactor(core): moves incremental hydration codebase to better locations (#58...560282afix(compiler): control flow nodes with root at the end projected incorrectly ...Updates
@angular/formsfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/forms's releases.... (truncated)
Changelog
Sourced from
@angular/forms's changelog.... (truncated)
Commits
93c3f7abuild: remove usages ofuseDefineForClassFields: false(#58297)1f45338Revert "fix(forms): fix FormRecord type inference (#50750)" (#58315)79d9be3Revert "feat(forms): add ability to clear a FormRecord (#50750)" (#58315)a5b0394Revert "test(forms): add unit test (#50750)" (#58315)b0c4c1ftest(forms): add unit test (#50750)3e7d724feat(forms): add ability to clear a FormRecord (#50750)18b6f33fix(forms): fix FormRecord type inference (#50750)09df589refactor(core): Migrate all packages with theexplicit-standalone-flagsche...186b524docs: add info onAbstractControl.sourcetype. (#58094)84b6896refactor(platform-server): Add an ssr benchmark setup. (#57647)Updates
@angular/platform-browserfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/platform-browser's releases.... (truncated)
Changelog
Sourced from
@angular/platform-browser's changelog.... (truncated)
Commits
c36a1c0fix(platform-browser): correctly add external stylesheets to ShadowDOM compon...917e99ddocs(platform-browser): update usage notes for incremental hydration (#58339)19edf2cfeat(core): add syntactic sugar for initializers (#53152)69fc5aefeat(core): Add incremental hydration public api (#58249)9544930refactor(core): add incremental hydration infrastructure (#58193)b542f15docs: removed typos of withHttpTransferCacheOptions description (#58244)09df589refactor(core): Migrate all packages with theexplicit-standalone-flagsche...5c61f46refactor(platform-browser): remove deprecated `BrowserModule.withServerTransi...84b6896refactor(platform-server): Add an ssr benchmark setup. (#57647)2545743refactor(core): support external runtime styles via a component feature (#57922)Updates
@angular/platform-browser-dynamicfrom 15.2.10 to 19.0.0Release notes
Sourced from
@angular/platform-browser-dynamic's releases.... (truncated)
Changelog
Sourced from
@angular/platform-browser-dynamic's changelog.