[Snyk] Fix for 1 vulnerabilities

[saumilmac]

Snyk has created this PR to fix 1 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
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[saumilmac]

This is a massive upgrade across six major versions of Angular (v10 to v16) and five major versions of node-sass. It includes a very large number of significant breaking changes that will require substantial code and configuration refactoring.

Key Breaking Changes for @angular/cli and @angular-devkit/build-angular (v10 to v16):

• View Engine Removed: As of v13, the legacy View Engine is completely removed. All libraries and application code must be Ivy-compatible. The Angular Compatibility Compiler (ngcc) is also removed in v16.
• Node.js and TypeScript Versions: Support for older Node.js and TypeScript versions has been dropped incrementally. Angular v16 requires Node.js v16 or v18 and TypeScript v4.9 or later.
• IE11 Support Removed: Support for Internet Explorer 11 was deprecated in v12 and completely removed in v13. This eliminates the need for differential loading and IE-specific polyfills.
• Build & Configuration Changes:
  • ng build now defaults to production builds.
  • The angular.json configuration has seen numerous changes, including the removal of environment.ts file replacements by default and deprecated options.
  • Standalone Components, introduced in v14 and stable in v15, are now the recommended way to build applications, reducing the reliance on NgModule.
• Tooling and API Changes:
  • TSLint and Codelyzer Removed: Migrated to ESLint in v11.
  • Protractor Deprecated: Support for Protractor for e2e tests was removed in v12.
  • Strict Mode by Default: New projects are created with strict mode enabled since v12.

Key Breaking Changes for node-sass (v4 to v9):

• node-sass is Deprecated: The node-sass package (based on LibSass) is deprecated and no longer recommended. The Angular CLI switched to the sass package (Dart Sass) as the default implementation in v12.
• Node.js Support: Each major version of node-sass drops support for older, end-of-life Node.js versions. Version 9 requires Node.js 14, 16, 18, or 19.

Recommendation: This upgrade cannot be performed in a single step. It is highly recommended to follow the official Angular Update Guide at update.angular.io and perform the migration one major version at a time. The ng update command will handle many, but not all, of the required code modifications. The most significant action is to replace node-sass with the sass package.

npm uninstall node-sass
npm install sass --save-dev

Due to the scale and complexity of these changes, this upgrade should be treated as a major project requiring extensive testing and refactoring.

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