fix(deps): update dependency angular-html-parser to v3 #3869
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:
~2.1.0
->~3.0.0
Release Notes
prettier/angular-html-parser
v3.0.0
Compare Source
Blog post "Angular v13 is now available".
Breaking Changes
common
SpyLocation
used by theRouterTestingModule
has changedto match the behavior of browsers. It no longer emits a 'popstate' event
when
Location.go
is called. In addition,simulateHashChange
nowtriggers both a
hashchange
and apopstate
event.Tests which use
location.go
and expect the changes to be picked up bythe
Router
should likely change tosimulateHashChange
instead.Each test is different in what it attempts to assert so there is no
single change that works for all tests. Each test using the
SpyLocation
tosimulate browser URL changes should be evaluated on a case-by-case basis.
core
TypeScript versions older than 4.4.2 are no longer supported.
NodeJS versions older than
v12.20.0
are no longersupported due to the Angular packages using the NodeJS package exports
feature with subpath patterns.
The
WrappedValue
class can no longer be imported from@angular/core
,which may result in compile errors or failures at runtime if outdated
libraries are used that are still using
WrappedValue
. The usage ofWrappedValue
should be removed as no replacement is available.forms
FormControlStatus
has been introduced, which is a union of all possible status strings for form controls.AbstractControl.status
has been narrowed fromstring
toFormControlStatus
, andstatusChanges
has been narrowed fromObservable<any>
toObservable<FormControlStatus>
. Most applications should consume the new types seamlessly. Any breakage caused by this change is likely due to one of the following two problems: (1) the app is comparingAbstractControl.status
against a string which is not a valid status; or, (2) the app is usingstatusChanges
events as if they were something other than strings.router
The default url serializer would previously drop
everything after and including a question mark in query parameters. That
is, for a navigation to
/path?q=hello?&other=123
, the queryparams would be parsed to just
{q: 'hello'}
. This isincorrect because the URI spec allows for question mark characers in
query data. This change will now correctly parse the params for the
above example to be
{v: 'hello?', other: '123'}
.Previously
null
andundefined
inputs forrouterLink
wereequivalent to empty string and there was no way to disable the link's
navigation.
In addition, the
href
is changed from a propertyHostBinding()
to anattribute binding (
HostBinding('attr.href')
). The effect of thischange is that
DebugElement.properties['href']
will now return thehref
value returned by the native element which will be the full URLrather than the internal value of the
RouterLink
href
property.When storing and retrieving a
DetachedRouteHandle
, the Router traversesthe
Route
children in order to correctly allow storing a parent route whenthere are several possible child
Route
configs that can be stored. This allowsa
RouteReuseStrategy
to store a parentRoute
and a child, while preservingthe ability to change the child route while restoring the parent. Some
implementations of
RouteReuseStrategy
will need to be updated to correctlystore and retrieve the
DetachedRouteHandle
of descendants as well as the storedparent
ActivatedRouteSnapshot
. Previously, theRouter
would only storethe parent, making it impossible to change descendant paths when a stored parent
was retrieved. See #20114.
The router will no longer replace the browser URL when a new navigation
cancels an ongoing navigation. This often causes URL flicker and was
only in place to support some AngularJS hybrid applications. Hybrid
applications which rely on the
navigationId
being present on initialnavigations that were handled by the Angular router should instead
subscribe to
NavigationCancel
events and perform thelocation.replaceState
themselves to addnavigationId
to the Routerstate.
In addition, tests which assert
urlChanges
on theSpyLocation
mayneed to be adjusted to account for the
replaceState
which is no longertriggered.
It is no longer possible to use
Route.loadChildren
using a stringvalue. The following supporting classes were removed from
@angular/core
:NgModuleFactoryLoader
SystemJsNgModuleFactoryLoader
The
@angular/router
package no longer exports these symbols:SpyNgModuleFactoryLoader
DeprecatedLoadChildren
The signature of the
setupTestingRouter
function from@angular/core/testing
has been changed to drop itsNgModuleFactoryLoader
parameter, as an argument for that parameter can no longer be created.
service-worker
SwUpdate#activateUpdate
andSwUpdate#checkForUpdate
changed toPromise<boolean>
.Although unlikely, it is possible that this change will cause TypeScript type-checking to fail in
some cases. If necessary, update your types to account for the new
return type.
Deprecations
core
Angular no longer requires component factories to dynamically create components. The factory-based signature of the
ViewContainerRef.createComponent
function is deprecated in favor of a different signature that allows passing component classes instead.The
getModuleFactory
function is deprecated in favor of thegetNgModuleById
one. With Ivy, it's possible to work with NgModule classes directly, without retrieving corresponding factories, so thegetNgModuleById
should be used instead.Ivy made it possible to avoid the need to resolve Component and NgModule factories. Framework APIs allow to use Component and NgModule Types directly. As a result, the
PlatformRef.bootstrapModuleFactory
and a factory-based signature of theApplicationRef.bootstrap
method are now obsolete and are now deprecated. ThePlatformRef.bootstrapModuleFactory
calls can be replaced withPlatformRef.bootstrapModule
ones. TheApplicationRef.bootstrap
method allows to provide Component Type, so this can be used a replacement for the factory-based calls.In ViewEngine, JIT compilation required special providers (like
Compiler
,CompilerFactory
, etc) to be injected in the app and corresponding methods to be invoked. With Ivy, JIT compilation takes place implicitly if the Component, NgModule, etc. have not already been AOT compiled. Those special providers were made available in Ivy for backwards-compatibility with ViewEngine to make the transition to Ivy smoother. Since ViewEngine is deprecated and will soon be removed, those symbols are now deprecated as well:ModuleWithComponentFactories
Compiler
CompilerFactory
JitCompilerFactory
NgModuleFactory
Important note: this deprecation doesn't affect JIT mode in Ivy (JIT remains available with Ivy).
aotSummaries
usage in TestBed is deprecated and will be removed in a future version of Angular.platform-server
renderModuleFactory
symbol in@angular/platform-server
is no longer necessary as of Angular v13.The
renderModuleFactory
calls can be replaced withrenderModule
.service-worker
SwUpdate#activated
observable is deprecated.The
SwUpdate#activated
observable only emits values as a direct response to callingSwUpdate#activateUpdate()
and was only useful for determining whether the call resulted in anupdate or not. Now, the return value of
SwUpdate#activateUpdate()
can be used to determine theoutcome of the operation and therefore using
SwUpdate#activated
does not offer any benefit.SwUpdate#availalbe
observable is deprecated.The new
SwUpdate#versionUpdates
observable provides the same information and more. Therefore, itis possible to rebuild the same behavior as
SwUpdate#availalbe
using the events emitted bySwUpdate#versionUpdates
and filtering forVersionReadyEvent
events.As a result, the
SwUpdate#availalbe
observable is now redundant.renderModuleFactory
(#43757)bazel
strict_templates
andexperimental_extended_template_diagnostics
tong_module()
rule (#43582)ng_package
targets (#43764)esm2020
andes2020
conditions in APF package exports (#43740)ng_package
rule (#43431)ng_module
(#43431)common
compiler
compiler-cli
ngc
to pass the build when only warnings are emitted (#43673)core
createNgModuleRef
function to createNgModuleRef
based on NgModule class (#43580)getNgModuleById
function to retrieve loaded NgModules by id (#43580)InjectFlags
argument inNodeInjector.get()
(#41592)WrappedValue
(#43507)elements
ng-add
schematic (#43975)@angular/platform-browser
peer dependency (#43975)forms
null
) (#42978)language-service
SafePropertyRead
when applying the optional chaining (#43321)migrations
router
popstate
events fromLocation
subscription (#43328)loadChildren
string syntax (#43591)service-worker
SwUpdate#activeUpdate
andSwUpdate#checkForUpdate
should have a meaningful outcome (#43668)Special Thanks
Ahmed Ayed, Alan Agius, Alex Rickabaugh, Andrew Kushnir, Andrew Scott, Bjarki, Charles Lyding, Dmitrij Kuba, Doug Parker, Dylan Hunn, George Kalpakas, Jessica Janiuk, Jochen Kraushaar, Joe Martin (Crowdstaffing), Joey Perrott, Jon Rimmer, JoostK, Kristiyan Kostadinov, Maximilian Köller, Paul Gschwendtner, Pei Wang, Pete Bacon Darwin, Tomasz Domański, Willy Schott, anandtiwary, dario-piotrowicz, iRealNirmal, ivanwonder, krzysztof-grzybek, mgechev and vthinkxie
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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.