chore(deps): update angular major to v19 (major) #2346
+3,239
−954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
18.2.12
->19.0.2
18.2.12
->19.0.2
18.2.12
->19.0.2
18.2.12
->19.0.0
18.2.12
->19.0.2
18.2.12
->19.0.0
^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^16.2.0 || ^17.0.0 || ^18.0.0
->^16.2.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^15.2.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^15.2.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^17.1.0 || ^18.0.0
->^17.1.0 || ^18.0.0 || ^19.0.0
^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^16.2.0 || ^17.0.0 || ^18.0.0
->^16.2.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^15.2.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^15.2.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
^17.1.0 || ^18.0.0
->^17.1.0 || ^18.0.0 || ^19.0.0
^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0
->^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.0
18.2.12
->19.0.2
Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v19.0.2
Compare Source
v19.0.1
Compare Source
@angular-devkit/build-angular
@angular/build
sha256
instead ofsha-256
as hash algorithm name@angular/ssr
./
v19.0.0
Compare Source
Breaking Changes
@schematics/angular
@angular-devkit/build-angular
The
browserTarget
option has been removed from the DevServer and ExtractI18n builders.buildTarget
is to be used instead.Protractor is no longer supported.
Protractor was marked end-of-life in August 2023 (see https://protractortest.org/). Projects still relying on Protractor should consider migrating to another E2E testing framework, several support solid migration paths from Protractor.
@angular-devkit/core
The deprecated
fileBuffer
function is no longer available. Update your code to usestringToFileBuffer
instead to maintain compatibility.Note: that this change does not affect application developers.
@angular/build
@angular/localize/init
polyfill will no longer be added automatically to projects. To prevent runtime issues, ensure that this polyfill is manually included in the "polyfills" section of your "angular.json" file if your application relies on Angular localization features.@angular/ssr
The
CommonEngine
API now needs to be imported from@angular/ssr/node
.Before
After
@angular-devkit/schematics-cli
@schematics/angular
withEventReplay()
inprovideClientHydration
for new SSR appsbrowser
builder@angular/ssr
featuredeclaration
andsourceMap
from default tsconfigexpress
@angular/cli
@angular-devkit/architect
@angular-devkit/build-angular
browser-sync
is not installedbrowserTarget
@angular-devkit/core
fileBuffer
function in favor ofstringToFileBuffer
@angular/build
sass
tostylePreprocessorOptions
in application builderoutputMode
option to the application builderssr.experimentalPlatform
optionssr.entry
during prerendering to enable access to local API routesssr.entry
in Vite dev-server when available--prerendering
or--app-shell
are no-opsindex.csr.html
is always generated when prerendering or SSR are enabled--import
from execArgv when spawning workersAPP_BASE_HREF
correctly in prerendered routesngServerMode
during vite prebundling--no-server
via command linereqHandler
for server.ts request handling@angular/localize/init
polyfill and related warnings@angular/ssr
createRequestHandler
andcreateNodeRequestHandler
utilitiesgetHeaders
Method toAngularAppEngine
andAngularNodeAppEngine
for handling pages static headersisMainModule
functionAngularAppEngine
as public APIwriteResponseToNodeResponse
andcreateWebRequestFromNodeRequest
in public APIAngularServerApp
AngularNodeAppEngine
API for Node.js integrationCommonEngine
API to/node
entry-point@angular/platform-server
provideServerRoutesConfig
in browser contextRESPONSE_INIT
,REQUEST
, andREQUEST_CONTEXT
tokensnull
to avoid requiring them to be set to optionalbootstrap is not a function
errorRenderMode.AppShell
angular/angular (@angular/animations)
v19.0.0
Compare Source
Breaking Changes
compiler
this.foo
property 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.
standalone: false
for declarations that are currently declared in@NgModule
s.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 toPendingTasks
.The
autoDetect
feature ofComponentFixture
will nowattach the fixture to the
ApplicationRef
. As a result, errors duringautomatic 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 emptyprojectableNodes
.projectableNodes
in thecreateComponent
API, the default fallback contentof the
ng-content
will be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')
as aprojectableNode
.Errors that are thrown during
ApplicationRef.tick
will now be rethrown when using
TestBed
. These errors should beresolved by ensuring the test environment is set up correctly to
complete change detection successfully. There are two alternatives to
catch the errors:
it synchronously and expect the error. For example, a jasmine test
could write
expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
TestBed
will reject any outstandingComponentFixture.whenStable
promises. A jasmine test,for example, could write
expectAsync(fixture.whenStable()).toBeRejected()
.As a last resort, you can configure errors to not be rethrown by
setting
rethrowApplicationErrors
tofalse
inTestBed.configureTestingModule
.The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use
fakeAsync
: these timers will now be visible tofakeAsync
and can be affected by
tick
orflush
.The deprecated
factories
property inKeyValueDiffers
has been removed.elements
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.
localize
name
option in theng add
@localize`` schematic has been removed in favor of theproject
option.platform-browser
BrowserModule.withServerTransition
method has been removed. Please use theAPP_ID
DI token to set the application id instead.router
Router.errorHandler
property has been removed.Adding an error handler should be configured in either
withNavigationErrorHandler
withprovideRouter
or theerrorHandler
property in the extra options of
RouterModule.forRoot
. In addition,the error handler cannot be used to change the return value of the
router navigation promise or prevent it from rejecting. Instead, if you
want to prevent the promise from rejecting, use
resolveNavigationPromiseOnError
.Resolve
interface now includesRedirectCommand
.common
compiler
typeof
keyword in template expressions. (#58183)this.a
should always refer to class propertya
(#55183):host
parsing in pseudo-selectors (#58681)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.