[Snyk] Fix for 4 vulnerabilities

[saumilmac]

Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• frontend/package.json
• frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18313044	828
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070	828
	Directory Traversal SNYK-JS-POSTCSS-18313036	721
	Directory Traversal SNYK-JS-POSTCSS-18313038	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Directory Traversal

[saumilmac]

This is a massive upgrade across 10 major versions of Angular and a deprecated package, representing a full framework migration rather than a simple dependency update. Significant, manual refactoring is required.

1. Angular CLI & DevKit (v10 → v19/v20): HIGH RISK

This jump spans from Angular v10 to v20 and introduces a vast number of breaking changes. A direct update is not feasible; the official Angular guidance is to upgrade one major version at a time.

Key breaking changes include:

• Mandatory Migration Path: You must follow the official Angular Update Guide to migrate incrementally (v10 → v11, v11 → v12, and so on). A direct jump will fail.
• Node.js & TypeScript: Required versions have changed significantly. Angular 20 requires Node.js v20.11+ and TypeScript v5.8+. [3, 11]
• Build System & Configuration: The build process has fundamentally changed, with the introduction of the esbuild-based builder and the new @angular/build package in v20. [3]
• Standalone Components: The architecture has shifted from NgModules to Standalone Components, which became the default in v15.
• New Control Flow Syntax: Angular 17 introduced new @if, @for, and @switch syntax. The old *ngIf and *ngFor directives are deprecated in v20. [1, 15]
• Testing Framework: The Karma test runner is no longer included by default as of v20, in favor of Jest and Vitest. [3]

2. node-sass (v4.14.1 → v9.0.0): HIGH RISK

• Package Deprecated: node-sass is deprecated and no longer supported for new features. The entire ecosystem has moved to the sass (Dart Sass) package. [13]
• Angular CLI Migration: Angular CLI automatically switched from node-sass to sass in version 12. Upgrading Angular past v11 requires replacing this package. [2]

Recommendation: This upgrade cannot be merged directly. It requires a dedicated migration project. Developers must follow the official Angular Update Guide to perform a sequential, version-by-version upgrade. This process will involve significant code refactoring, configuration changes, and testing at each step.

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