[Snyk] Security upgrade @angular/common from 18.2.13 to 19.2.16 #176
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-lock.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-ANGULARCOMMON-14135651
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
chargebee-js-angular/package.jsonchargebee-js-angular/package-lock.jsonThis major version upgrade introduces significant architectural changes by making Standalone APIs the default for all components, directives, and pipes. It also includes updates to core reactivity primitives and dependency requirements.
Highlights:
ng updatecommand will migrate most projects automatically, but applications with complex or custom NgModule declarations will require manual review and may need to explicitly setstandalone: false.effect()Function Change: TheallowSignalWritesflag has been removed from theeffect()function. Signal writes are now allowed by default within an effect, which may alter the behavior of existing reactive code.Source: Angular Documentation
Recommendation: Run
ng update @angular/core@19 @angular/cli@19and perform a full functional test of the application, paying close attention to module-dependent features and reactive effects. Also, ensure your environment meets the new Node.js (18.19.0+) and TypeScript (5.5+) requirements.Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-ANGULARCOMMON-14135651
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.