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)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps @angular/forms from 18.0.6 to 19.0.0.
Release 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)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show