chore(deps): update angular monorepo to v21 (major)#792
Conversation
|
✅ Deploy Preview for unpic-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for unpic-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for unpic-angular ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
23dd1a6 to
9d27a77
Compare
9d27a77 to
38cc950
Compare
dcf914a to
074e8e5
Compare
079e7e5 to
11f71f8
Compare
f44912f to
0102cae
Compare
0102cae to
1d9b582
Compare
7c5f513 to
e798e61
Compare
c290847 to
11d8053
Compare
87ac162 to
e2525b4
Compare
3c0d12f to
2b4cd62
Compare
7d6935f to
ef166fe
Compare
8e5645c to
8847623
Compare
42cd16d to
45e4b7f
Compare
5e4ebf8 to
0088818
Compare
67c6525 to
1d22920
Compare
d1d52d3 to
66e5652
Compare
- Update all Angular tooling packages to v21 (cli, devkit, ng-packagr) - Add @angular/compiler to devDependencies - Update tsconfig.json to use moduleResolution: bundler (required for v21) - Update TypeScript to 5.9 (required for Angular 21) - Add peerDependencies for @angular/core (^14.0.0 - ^21.0.0) - Fix types path in package.json exports - Update examples/angular to Angular 21 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
66e5652 to
1db3e39
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
@unpic/angular
@unpic/astro
@unpic/core
@unpic/lit
@unpic/preact
@unpic/qwik
@unpic/react
@unpic/solid
@unpic/svelte
@unpic/vue
@unpic/webc
commit: |
- Remove module/typings fields that conflicted with exports - Run publint from package root so workspace protocol resolves - Add sideEffects: false 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
…tion Add module and typings root-level fields for compatibility with Angular projects using moduleResolution: "node" (Angular 14-17 default). Keeps exports for modern bundler resolution. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
This PR contains the following updates:
^19.1.1->^21.0.3^19.1.1->^21.0.3Release Notes
angular/angular (@angular/compiler-cli)
v21.0.3Compare Source
compiler-cli
core
[field]binding instructions (#65599)forms
FormUiControlsignals[field]bindings (#65599)http
router
v21.0.2Compare Source
compiler
attributeNameand MathML/SVG URLsv21.0.1Compare Source
compiler-cli
core
platformBrowserDynamicDOCUMENTforCSP_NONCEforms
Fielddirectivetypebindings on signal form controlshttp
migrations
v21.0.0Compare Source
Blog post "Announcing Angular v21".
Breaking Changes
common
TestBednow provides a fakePlatformLocationimplementation that supports the Navigation API. This may break some
tests, though we have not observed any failures internally. You can revert to the
old default for
TestBedby providing theMockPlatformLocationfrom@angular/common/testingin your providers:{provide: PlatformLocation, useClass: MockPlatformLocation}ngComponentOutletContentis now of typeNode[][] | undefinedinstead ofany[][] | undefined.compiler-cli
"typeCheckHostBindings": falsein theangularCompilerOptionssection of your tsconfig.the
emitDeclarationOnlyTS compiler option is enabled as this mode isnot supported.
core
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
A schematic is provided to automatically update
main.server.tsfiles to pass theBootstrapContextto thebootstrapApplicationcall.In addition,
getPlatform()anddestroyPlatform()will now returnnulland be a no-op respectively when running in a server environment.Using a combination of
provideZoneChangeDetectionwhile also removing ZoneJS polyfills will no longer result in the
internal scheduler being disabled. All Angular applications now
consistenly use the same scheduler, and those with the Zone change detection
provider include additional automatic scheduling behaviors based on
NgZone stabilization.
(test only) - Using
provideZoneChangeDetectionin theTestBed providers would previously prevent
TestBedfrom rethrowingerrors as it should. Errors in the test will now be rethrown, regardless
of the usage of
provideZoneChangeDetection. Tests should be adjusted toprevent or account for these errors. As in previous major versions,
this behavior can be disabled with
rethrowApplicationErrors: falseinconfigureTestingModuleas a last resort.ignoreChangesOutsideZoneis no longer available as anoption for configuring ZoneJS change detection behavior.
Angular no longer provides a change detection scheduler
for ZoneJS-based change detection by default. Add
provideZoneChangeDetectionto the providers of yourbootstrapApplicationfunction or yourAppModule(if usingbootstrapModule). This provider addition will be covered by anautomated migration.
moduleIdwas removed fromComponentmetadata.The
interpolationoption on Components has been removed. Only the default{{ ... }}is now supported.elements
Fix signal input getter behavior in custom elements.
Before this change, signal inputs in custom elements required function calls to access their values (
elementRef.newInput()), while decorator inputs were accessed directly (elementRef.oldInput). This inconsistency caused confusion and typing difficulties.The getter behavior has been standardized so signal inputs can now be accessed directly, matching the behavior of decorator inputs:
Before:
elementRef.oldInputelementRef.newInput()After:
elementRef.oldInputelementRef.newInputforms
platform-browser
ApplicationConfigexport from@angular/platform-browserhas been removed.Please import
ApplicationConfigfrom@angular/coreinstead.router
lastSuccessfulNavigationis now a signal and needs to be invokedmicrotasks to complete. Tests have been found to often be highly
dependent on the exact timing of navigation completions with respect to
the microtask queue. The most common fix for tests is to ensure all
navigations have been completed before making assertions. On rare
occasions, this can also affect production applications. This can be
caused by multiple subscriptions to router state throughout the application,
both of which trigger navigations that happened to not conflict with the
previous timing.
upgrade
UpgradeAdapteris no longer available. Useupgrade/staticinsteadzone.js
Deprecations
http
HttpResponseBase.statusTextis deprecatedcommon
ngComponentOutletContent(#63674)ngModuleFactoryinput ofNgComponentOutlet(#62838)compiler
compiler-cli
@defertriggers (#64069)emitDeclarationOnlyTS compiler option enabled (#61609)core
bootstrapModuleoptions (#64354)BootstrapContextfor improved server bootstrapping (#63562)@foriteration over field is reactive (#64113)moduleIdfrom Component metadata (#63482)interpolationoption on Components. (#63474)elements
forms
debounce()rule for signal formsFormResetEventwhen resetting control (#64024)ControlValueAccessor(#64471)[field]binding instructions (#64351)http
HttpResponseBase.statusText(#64176)language-server
language-service
migrations
platform-browser
ApplicationConfigexport (#63529)router
lastSuccessfulNavigationto signal (#63057)UrlSerializerhandling of query parameters (#64449)upgrade
v20.3.15Compare Source
compiler
attributeNameand MathML/SVG URLsv20.3.14Compare Source
http
v20.3.13Compare Source
v20.3.12Compare Source
v20.3.11Compare Source
common
compiler
core
v20.3.10Compare Source
compiler-cli
migrations
v20.3.9Compare Source
v20.3.7Compare Source
animations
Element.animateexceptions (#64506)compiler
compiler-cli
core
router
v20.3.6Compare Source
core
platform-browser
DomEventsPluginshould always be the last plugin to be called forsupports(). (#50394)v20.3.5Compare Source
compiler-cli
core
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.