[Snyk] Security upgrade @angular-devkit/build-angular from 0.1000.8 to 22.1.1

[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

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	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:

🦉 Directory Traversal

[saumilmac]

This is a massive upgrade across more than 10 major versions of Angular, from v10 to a hypothetical v22. This update is extremely high-risk and will require a multi-step migration process, as the Angular build system has been fundamentally rewritten.

Key Breaking Changes:

• Build System Overhaul: The build process has evolved from Webpack 4 (in v10) to Webpack 5 (v12+), and now defaults to a new, faster esbuild-based application builder in v17+. This new builder unifies server-side rendering and static-site generation and requires significant configuration changes in angular.json. [1]
• Ivy Engine is Mandatory: As of v13, the legacy View Engine has been completely removed. All code and dependencies must be compatible with the Ivy compilation and rendering engine. [2]
• Node.js and TypeScript Requirements: Support for older Node.js versions has been dropped. Angular v17+ requires Node.js v18.13 or newer. You must upgrade your development and CI/CD environments. [3]
• Standalone APIs as Default: Starting with v17, applications are structured using Standalone Components, Directives, and Pipes by default, moving away from the traditional NgModule-based architecture. [1]

Recommendation: A direct version jump is not possible. You must perform a sequential upgrade, one major version at a time, using the official Angular Update Guide at update.angular.io. Start by running ng update @angular/core@11 @angular/cli@11 and resolve breaking changes before moving to v12, and so on. This is a major refactoring effort that must be planned carefully.

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