chore(deps): update all dependencies #269
Merged
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.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.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^0.61.0->^0.62.0^0.61.0->^0.62.0^0.61.0->^0.62.0^0.61.0->^0.62.0^0.61.0->^0.62.04.5.1->4.5.3Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v19.0.2Compare Source
@schematics/angular
@angular/build
injectto prevent code reorderinggetPrerenderParamsis undefined@angular/ssr
v19.0.1Compare Source
@angular-devkit/build-angular
@angular/build
sha256instead ofsha-256as hash algorithm name@angular/ssr
./v19.0.0Compare Source
Breaking Changes
@schematics/angular
@angular-devkit/build-angular
The
browserTargetoption has been removed from the DevServer and ExtractI18n builders.buildTargetis 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
fileBufferfunction is no longer available. Update your code to usestringToFileBufferinstead to maintain compatibility.Note: that this change does not affect application developers.
@angular/build
@angular/localize/initpolyfill 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
CommonEngineAPI now needs to be imported from@angular/ssr/node.Before
After
@angular-devkit/schematics-cli
@schematics/angular
withEventReplay()inprovideClientHydrationfor new SSR appsbrowserbuilder@angular/ssrfeaturedeclarationandsourceMapfrom default tsconfigexpress@angular/cli
@angular-devkit/architect
@angular-devkit/build-angular
browser-syncis not installedbrowserTarget@angular-devkit/core
fileBufferfunction in favor ofstringToFileBuffer@angular/build
sasstostylePreprocessorOptionsin application builderoutputModeoption to the application builderssr.experimentalPlatformoptionssr.entryduring prerendering to enable access to local API routesssr.entryin Vite dev-server when available--prerenderingor--app-shellare no-opsindex.csr.htmlis always generated when prerendering or SSR are enabled--importfrom execArgv when spawning workersAPP_BASE_HREFcorrectly in prerendered routesngServerModeduring vite prebundling--no-servervia command linereqHandlerfor server.ts request handling@angular/localize/initpolyfill and related warnings@angular/ssr
createRequestHandlerandcreateNodeRequestHandlerutilitiesgetHeadersMethod toAngularAppEngineandAngularNodeAppEnginefor handling pages static headersisMainModulefunctionAngularAppEngineas public APIwriteResponseToNodeResponseandcreateWebRequestFromNodeRequestin public APIAngularServerAppAngularNodeAppEngineAPI for Node.js integrationCommonEngineAPI to/nodeentry-point@angular/platform-serverprovideServerRoutesConfigin browser contextRESPONSE_INIT,REQUEST, andREQUEST_CONTEXTtokensnullto avoid requiring them to be set to optionalbootstrap is not a functionerrorRenderMode.AppShellangular/angular (@angular/animations)
v19.0.1Compare Source
compiler-cli
core
forms
language-service
migrations
v19.0.0Compare Source
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.
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 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.
createComponentwill now render default fallback with emptyprojectableNodes.projectableNodesin thecreateComponentAPI, the default fallback contentof the
ng-contentwill be rendered if present. To prevent rendering the default content, passdocument.createTextNode('')as aprojectableNode.Errors that are thrown during
ApplicationRef.tickwill 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()TestBedwill reject any outstandingComponentFixture.whenStablepromises. 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
rethrowApplicationErrorstofalseinTestBed.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 tofakeAsyncand can be affected by
tickorflush.The deprecated
factoriesproperty inKeyValueDiffershas 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
nameoption in theng add@localize`` schematic has been removed in favor of theprojectoption.platform-browser
BrowserModule.withServerTransitionmethod has been removed. Please use theAPP_IDDI token to set the application id instead.router
Router.errorHandlerproperty has been removed.Adding an error handler should be configured in either
withNavigationErrorHandlerwithprovideRouteror theerrorHandlerproperty 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.Resolveinterface now includesRedirectCommand.common
compiler
typeofkeyword in template expressions. (#58183)this.ashould always refer to class propertya(#55183):hostparsing in pseudo-selectors (#58681):host:host-context(.foo)(#58681)compiler-cli
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.