New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update frontendDevDependencies (major) #519
base: master
Are you sure you want to change the base?
Conversation
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: frontend/package-lock.json
|
2aa30f5
to
6c1b54d
Compare
514a955
to
a5b4f9b
Compare
a5b4f9b
to
a87c8f7
Compare
b004a74
to
c38f2f6
Compare
ee76e04
to
c0ec5d3
Compare
c0ec5d3
to
9d811c1
Compare
9d811c1
to
f84b1b0
Compare
f84b1b0
to
05e0601
Compare
|
This PR contains the following updates:
^17.0.8
->^18.0.0
^17.0.8
->^18.0.0
^17.0.8
->^18.0.0
~3.10.0
->~5.1.0
4.0.0
->5.1.2
~4.0.0
->~5.1.0
~1.7.0
->~2.1.0
Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v18.0.1
Compare Source
v18.0.0
Compare Source
Breaking Changes
@angular/cli
ng doc
command has been removed without a replacement. To perform searches, please visit www.angular.dev@angular-devkit/build-angular
By default, the index.html file is no longer emitted in the browser directory when using the application builder with SSR. Instead, an index.csr.html file is emitted. This change is implemented because in many cases server and cloud providers incorrectly treat the index.html file as a statically generated page. If you still require the old behavior, you can use the
index
option to specify theoutput
file name.The support for the legacy Sass build pipeline, previously accessible via
NG_BUILD_LEGACY_SASS
when utilizing webpack-based builders, has been removed.Deprecations
@angular-devkit/schematics
NodePackageLinkTask
in@angular-devkit/schematics
. A custom task should be created instead.@angular/cli
ng dev
alias tong serve
--version
option@angular/build
package to update group listng version
commandng doc
command@schematics/angular
assets
withpublic
directory@angular-devkit/architect
@angular-devkit/build-angular
poll
option in the library builderindex.html
file in the browser directory when using SSR.@angular-devkit/schematics
NodePackageLinkTask
@angular/build
ansi-colors
andpicomatch
dependenciesv17.3.8
Compare Source
17.3.8 (2024-05-22)
@angular/cli
@angular-devkit/schematics
SchematicTestRunner.runExternalSchematic
fails with "The encoded data was not valid for encoding utf-8"v17.3.7
Compare Source
v17.3.6
Compare Source
@angular-devkit/build-angular
v17.3.5
Compare Source
v17.3.4
Compare Source
@angular-devkit/build-angular
v17.3.3
Compare Source
@schematics/angular
v17.3.2
Compare Source
@schematics/angular
@angular-devkit/build-angular
Internal server error: Invalid URL
when using a non localhost IPwebpack-dev-middleware
to6.1.2
v17.3.1
Compare Source
17.3.1 (2024-03-20)
@schematics/angular
@angular-devkit/build-angular
server
directory when SSR is enabledv17.3.0
Compare Source
@schematics/angular
@angular-devkit/build-angular
deployUrl
to application builderv17.2.3
Compare Source
@angular-devkit/build-angular
deployUrl
when using vite dev-serverv17.2.2
Compare Source
@angular-devkit/build-angular
v17.2.1
Compare Source
@angular-devkit/build-angular
mts
andcts
file replacementv17.2.0
Compare Source
@angular/cli
bun
package manager@schematics/angular
bun
package manager@angular-devkit/build-angular
.html
served with Vite dev-server@angular-devkit/schematics
bun
to known package managers@angular/create
bun
package managerv17.1.4
Compare Source
@angular/cli
package.json
duringng update
@angular-devkit/build-angular
v17.1.3
Compare Source
@angular-devkit/build-angular
./
baseHref when using vite based serverv17.1.2
Compare Source
@angular-devkit/build-angular
required
modules as externals importsoutput-path
when using esbuild based buildersv17.1.1
Compare Source
@angular/cli
@schematics/angular
@angular-devkit/build-angular
ENOENT: no such file or directory
on Windows during component rebuild@angular/ssr
v17.1.0
Compare Source
@schematics/angular
outputPath
---skip-install
and--ssr
@angular-devkit/build-angular
--no-browsers
in karma builderallowedCommonJsDependencies
@web/test-runner
builderbrowser-sync
as optional dependencyOPTIONS
requests to be proxied when usingvite
angular/angular (@angular/compiler-cli)
v18.0.0
Compare Source
Breaking Changes
animations
matchesElement
method has been removed fromAnimationDriver
as it is unused.common
isPlatformWorkerUi
andisPlatformWorkerApp
have been removed without replacement, as they serve no purpose since the removal of the WebWorker platform.compiler
compiler-cli
core
OnPush
views at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush
change detection strategy.OnPush
views at the root of the application need tobe marked dirty for their host bindings to refresh. Previously, the host
bindings were refreshed for all root views without respecting the
OnPush
change detection strategy.The
ComponentFixture
autoDetect
feature will nolonger refresh the component's host view when the component is
OnPush
and not marked dirty. This exposes existing issues in components which
claim to be
OnPush
but do not correctly callmarkForCheck
when theyneed to be refreshed. If this change causes test failures, the easiest
fix is to change the component to
ChangeDetectionStrategy.Default
.ComponentFixture.whenStable
now matches theApplicationRef.isStable
observable. Prior to this change, stabilityof the fixture did not include everything that was considered in
ApplicationRef
.whenStable
of the fixture will now include unfinishedrouter navigations and unfinished
HttpClient
requests. This will causetests that
await
thewhenStable
promise to time out when there areincomplete requests. To fix this, remove the
whenStable
,instead wait for another condition, or ensure
HttpTestingController
mocks responses for all requests. Try adding
HttpTestingController.verify()
before your
await fixture.whenStable
to identify the open requests.Also, make sure your tests wait for the stability promise. We found many
examples of tests that did not, meaning the expectations did not execute
within the test body.
In addition,
ComponentFixture.isStable
would synchronously switch totrue in some scenarios but will now always be asynchronous.
Angular will ensure change detection runs, even when the state update originates from
outside the zone, tests may observe additional rounds of change
detection compared to the previous behavior.
This change will be more likely to impact existing unit tests.
This should usually be seen as more correct and the test should be updated,
but in cases where it is too much effort to debug, the test can revert to the old behavior by adding
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
to the
TestBed
providers.Similarly, applications which may want to update state outside the zone
and not trigger change detection can add
provideZoneChangeDetection({schedulingMode: NgZoneSchedulingMode.NgZoneOnly})
to the providers in
bootstrapApplication
or addschedulingMode: NgZoneSchedulingMode.NgZoneOnly
to theBootstrapOptions
ofbootstrapModule
.When Angular runs change detection, it will continue to
refresh any views attached to
ApplicationRef
that are still marked forcheck after one round completes. In rare cases, this can result in infinite
loops when certain patterns continue to mark views for check using
ChangeDetectorRef.detectChanges
. This will be surfaced as a runtimeerror with the
NG0103
code.async
has been removed, usewaitForAsync
instead.The
ComponentFixture.autoDetect
feature now executeschange detection for the fixture within
ApplicationRef.tick
. This moreclosely matches the behavior of how a component would refresh in
production. The order of component refresh in tests may be slightly
affected as a result, especially when dealing with additional components
attached to the application, such as dialogs. Tests sensitive to this
type of change (such as screenshot tests) may need to be updated.
Concretely, this change means that the component will refresh before
additional views attached to
ApplicationRef
(i.e. dialog components).Prior to this change, the fixture component would refresh after other
views attached to the application.
The exact timing of change detection execution when
using event or run coalescing with
NgZone
is now the first of eithersetTimeout
orrequestAnimationFrame
. Code which relies on thistiming (usually by accident) will need to be adjusted. If a callback
needs to execute after change detection, we recommend
afterNextRender
instead of something like
setTimeout
.Newly created and views marked for check and reattached
during change detection are now guaranteed to be refreshed in that same
change detection cycle. Previously, if they were attached at a location
in the view tree that was already checked, they would either throw
ExpressionChangedAfterItHasBeenCheckedError
or not be refreshed untilsome future round of change detection. In rare circumstances, this
correction can cause issues. We identified one instance that relied on
the previous behavior by reading a value on initialization which was
queued to be updated in a microtask instead of being available in the
current change detection round. The component only read this value during
initialization and did not read it again after the microtask updated it.
Testability methods
increasePendingRequestCount
,decreasePendingRequestCount
andgetPendingRequestCount
have beenremoved. This information is tracked with zones.
http
By default we now prevent caching of HTTP requests that require authorization . To opt-out from this behaviour use the
includeRequestsWithAuthHeaders
option inwithHttpTransferCache
.Example:
platform-browser
StateKey
,TransferState
andmakeStateKey
have been removed from@angular/platform-browser
, use the same APIs from@angular/core
.platform-browser-dynamic
RESOURCE_CACHE_PROVIDER
APIs have been removed.platform-server
deprecated
platformDynamicServer
has been removed. Add animport @​angular/compiler
and replace the usage withplatformServer
deprecated
ServerTransferStateModule
has been removed.TransferState
can be use without providing this module.deprecated
useAbsoluteUrl
andbaseUrl
been removed fromPlatformConfig
. Provide and absoluteurl
instead.Legacy handling or Node.js URL parsing has been removed from
ServerPlatformLocation
.The main differences are;
pathname
is always suffixed with a/
.port
is empty whenhttp:
protocol and port in url is `8Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.