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.
Snyk has created this PR to upgrade multiple dependencies.
👯 The following dependencies are linked and will therefore be updated together.ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
@angular/animations
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 5 years ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
⚠️ This is a major version upgrade, and may be a breaking change | 23 days ago
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/common
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/compiler
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/core
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/forms
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/http
from 6.0.7 to 7.2.16 | 64 versions ahead of your current version
on 2020-01-08
@angular/platform-browser
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/platform-browser-dynamic
from 6.0.7 to 18.1.3 | 640 versions ahead of your current version
on 2024-07-31
@angular/router
from 6.0.7 to 18.1.3 | 642 versions ahead of your current version
on 2024-07-31
Issues fixed by the recommended upgrade:
SNYK-JS-ANGULARCORE-1070902
Release notes
Package name: @angular/animations
19.0.0-next.1 (2024-08-22)
compiler-cli
core
fakeAsync
(#56932)migrations
Breaking Changes
core
autoDetect
feature ofComponentFixture
will 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.
19.0.0-next.0 (2024-08-14)
core
router
routerOutletData
input toRouterOutlet
directive (#57051)Breaking Changes
core
Errors that are thrown during
ApplicationRef.tick
will 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()
TestBed
will reject any outstandingComponentFixture.whenStable
promises. 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
rethrowApplicationErrors
tofalse
inTestBed.configureTestingModule
.router
Router.errorHandler
property has been removed.Adding an error handler should be configured in either
withNavigationErrorHandler
withprovideRouter
or theerrorHandler
property 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
.Resolve
interface now includesRedirectCommand
.18.2.1 (2024-08-22)
core
fakeAsync
(#56932)migrations
18.2.0 (2024-08-14)
compiler
compiler-cli
jit: true
opt-out (#56892)@ NgModule
classes withjit: true
(#57212)core