Skip to content

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Jan 27, 2026

snyk-top-banner

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.json
  • chargebee-js-angular/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  575  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Directory Traversal

…-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-TAR-15032660
@snyk-io
Copy link
Author

snyk-io bot commented Jan 27, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@snyk-io
Copy link
Author

snyk-io bot commented Jan 27, 2026

Merge Risk: High

This upgrade spans two major versions of Angular and introduces significant breaking changes, including the removal of the Karma test runner and a mandatory Node.js version update.

  • @angular/cli 18.2.12 → 20.3.15 (high): This upgrade drops support for Node.js 18, requiring Node.js 20.11.1+ and TypeScript 5.8+. The default build system no longer supports the Karma test runner, which will cause ng test to fail. Additionally, components are now standalone by default.

  • ng-packagr 18.2.1 → 19.0.0 (medium): This version includes a significant overhaul of the internal stylesheet processing pipeline. While listed as a bug fix, the scope of this change could introduce unexpected issues in library builds with complex styling. [5]

Highlights:

  • Update Node.js and TypeScript: Your environment must use Node.js v20.11.1+ and TypeScript v5.8+. [9, 4]
  • Migrate Test Runner: Karma is no longer supported by default. You must either install a compatibility builder or migrate tests to a supported runner like Jest or Vitest. [9, 12]

Source: Angular and ng-packagr documentation, changelogs.
Recommendation: Plan for a test runner migration. Run ng update to apply automated migrations for standalone components and other deprecations, then validate build and test pipelines thoroughly.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants