fix(deps): update angular monorepo to v16 (major) #246
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:
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
6.0.3
->16.2.12
Release Notes
angular/angular (@angular/animations)
v16.2.12
Compare Source
animations
finish
listener once player is destroyed (#51136)common
compiler-cli
v16.2.11
Compare Source
core
providedIn
(#52365)router
RouterTestingHarness
should throw if a component is expected but navigation fails (#52357)v16.2.10
Compare Source
v16.2.9
Compare Source
forms
v16.2.8
Compare Source
language-service
ts.Project
reloads (#51912)service-worker
v16.2.7
Compare Source
core
service-worker
handleFetch
fails (#51885)v16.2.6
Compare Source
core
v16.2.5
Compare Source
v16.2.4
Compare Source
v16.2.3
Compare Source
animations
compiler-cli
core
language-service
v16.2.2
Compare Source
common
compiler-cli
core
router
canceledNavigationResolution: 'computed'
works on first page (#51441)v16.2.1
Compare Source
router
v16.2.0
Compare Source
benchpress
common
compiler
compiler-cli
core
router
fixture
of theRouterTestingHarness
(#50280)v16.1.9
Compare Source
v16.1.8
Compare Source
compiler
v16.1.7
Compare Source
http
Zone
is defined (#51119)v16.1.6
Compare Source
http
v16.1.5
Compare Source
animations
core
deref
returningnull
onRefactiveNode
. (#50992)platform-browser
REMOVE_STYLES_ON_COMPONENT_DESTROY
is enabled. (#51005)upgrade
takeUntil
on leaky subscription. (#50901)v16.1.4
Compare Source
core
setTimeout
when coalescing tasks in Node.js (#50820)upgrade
v16.1.3
Compare Source
core
elements
platform-browser
v16.1.2
Compare Source
http
v16.1.1
Compare Source
compiler-cli
core
migrations
v16.1.0
Compare Source
compiler
core
http
fetch
Backend for theHttpClient
(#50247)v16.0.6
Compare Source
core
v16.0.5
Compare Source
compiler
core
ngOnInit
correctly before server render (#50573)platform-server
v16.0.4
Compare Source
animations
common
core
ApplicationRef.isStable
to account for rendering pending tasks (#50425)v16.0.3
Compare Source
core
Self
flag inside embedded views with custom injectors (#50270)http
v16.0.2
Compare Source
core
isSignal
function (#50035)v16.0.1
Compare Source
core
v16.0.0
Compare Source
Blog post "Angular v16 is now available".
Breaking Changes
EventManager
methodaddGlobalEventListener
has been removed as it is not used by Ivy.bazel
common
MockPlatformLocation
is now provided by default in tests.Existing tests may have behaviors which rely on
BrowserPlatformLocation
instead. For example, direct access to thewindow.history
in either the test or the component rather than goingthrough the Angular APIs (
Location.getState()
). The quickest fix is toupdate the providers in the test suite to override the provider again
TestBed.configureTestingModule({providers: [{provide: PlatformLocation, useClass: BrowserPlatformLocation}]})
.The ideal fix would be to update the code to instead be compatible with
MockPlatformLocation
instead.Before the change, the following template was compiling:
However, it does not compile now because the 'xxx' property does not exist in 'MyContext', resulting in the error: 'Type '{ $implicit: string; xxx: string; }' is not assignable to type 'MyContext'.'
The solution is either:
XhrFactory
export from@angular/common/http
has been removed. UseXhrFactory
from@angular/common
instead.compiler
core
QueryList.filter now supports type guard functions, which will result in type narrowing. Previously if you used type guard functions, it resulted in no changes to the return type. Now the type would be narrowed, which might require updates to the application code that relied on the old behavior.
zone.js
versions0.11.x
and0.12.x
are not longer supported.entryComponents
has been deleted from the@NgModule
and@Component
public APIs. Any usages can be removed since they weren't doing anyting.ANALYZE_FOR_ENTRY_COMPONENTS
injection token has been deleted. Any references can be removed.ComponentRef.setInput will only set the input on the
component if it is different from the previous value (based on
Object.is
equality). If code relies on the input always being set, it should be
updated to copy objects or wrap primitives in order to ensure the input
value differs from the previous call to
setInput
.RendererType2.styles
no longer accepts a nested arrays.The
APP_ID
token value is no longer randomly generated. If you are bootstrapping multiple application on the same page you will need to set to provide theAPP_ID
yourself.The
ReflectiveInjector
and related symbols were removed. Please update the code to avoid references to theReflectiveInjector
symbol. UseInjector.create
as a replacement to create an injector instead.Node.js v14 support has been removed
Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.
platform-browser
BrowserTransferStateModule
was removed, since it's no longer needed. TheTransferState
class can be injected without providing the module. TheBrowserTransferStateModule
was empty starting from v14 and you can just remove the reference to that module from your applications.platform-server
Users that are using SSR with JIT mode will now need to add
import to @​angular/compiler
before bootstrapping the application.NOTE: this does not effect users using the Angular CLI.
renderApplication
method no longer accepts a root component as first argument. Instead, provide a bootstrapping function that returns aPromise<ApplicationRef>
.Before
Now
renderModuleFactory
has been removed. UserenderModule
instead.router
Scroll
event'srouterEvent
property may also bea
NavigationSkipped
event. Previously, it was only aNavigationEnd
event.
ComponentFactoryResolver
has been removed from Router APIs.Component factories are not required to create an instance of a component
dynamically. Passing a factory resolver via resolver argument is no longer needed
and code can instead use
ViewContainerRef.createComponent
without thefactory resolver.
RouterEvent
type is no longer present in theEvent
union type representing all router event types. If you have code using something likefilter((e: Event): e is RouterEvent => e instanceof RouterEvent)
, you'll need to update it tofilter((e: Event|RouterEvent): e is RouterEvent => e instanceof RouterEvent)
.ActivatedRoute
instances may need to be adjustedbecause Router.createUrlTree now does the right thing in more
scenarios. This means that tests with invalid/incomplete ActivatedRoute mocks
may behave differently than before. Additionally, tests may now navigate
to a real URL where before they would navigate to the root. Ensure that
tests provide expected routes to match.
There is rarely production impact, but it has been found that relative
navigations when using an
ActivatedRoute
that does not appear in thecurrent router state were effectively ignored in the past. By creating
the correct URLs, this sometimes resulted in different navigation
behavior in the application. Most often, this happens when attempting to
create a navigation that only updates query params using an empty
command array, for example
router.navigate([], {relativeTo: route, queryParams: newQueryParams})
. In this case, therelativeTo
propertyshould be removed.
Deprecations
core
makeStateKey
,StateKey
andTransferState
exports have been moved from@angular/platform-browser
to@angular/core
. Please update the imports.EnvironmentInjector.runInContext
is now deprecated, withrunInInjectionContext
functioning as a direct replacement:The
@Directive
/@Component
moduleId
property is nowdeprecated. It did not have any effect for multiple major versions and
will be removed in v17.
platform-browser
BrowserModule.withServerTransition
has been deprecated.APP_ID
should be used instead to set the application ID.NB: Unless, you render multiple Angular applications on the same page, setting an application ID is not necessary.
Before:
After:
ApplicationConfig
has moved, please importApplicationConfig
from@angular/core
instead.platform-server
PlatformConfig.baseUrl
andPlatformConfig.useAbsoluteUrl
platform-server config options are deprecated as these were not used.EventManager
methodaddGlobalEventListener
(#49645)common
XhrFactory
export fromhttp
entrypoint (#49251)compiler
extends
(#49125)compiler-cli
nSkipHydration
(#49512)core
assertInInjectionContext
(#49529)mergeApplicationConfig
method (#49253)NgZone
inbootstrapApplication
(#49557)moduleId
references (#49496)factories
property forIterableDiffers
: Breaking change (#49598)zone.js
versions<=0.12.0
(#49331)makeStateKey
,StateKey
andTransferState
(#49563)takeUntilDestroyed
in rxjs-interop (#49154)runInInjectionContext
and deprecate prior version (#49396)moduleId
@Component
property (#49496)Configuration
📅 Schedule: Branch creation - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, 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.