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

[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
	Directory Traversal SNYK-JS-POSTCSS-18512282	738

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 major upgrade spanning multiple significant versions of Angular, from v10 to a hypothetical v20. Such an upgrade is a massive undertaking involving substantial breaking changes, architectural shifts, and requires a version-by-version migration.

Key Breaking Changes Across Versions:

• Build System Overhaul: The build system has fundamentally changed. Webpack 5 was introduced in v12, and v17 replaces Webpack with a more performant esbuild and Vite-based system by default. This will require significant configuration changes in angular.json.
• View Engine Removed: Angular's legacy View Engine compiler was deprecated in v12 and completely removed in v13. All applications and libraries must use the Ivy rendering engine. The Angular Compatibility Compiler (ngcc) was also removed in v16, meaning libraries not compiled with Ivy are no longer supported.
• Standalone Components: Introduced in v14 and made stable in v15, Standalone Components, Directives, and Pipes are now the default and recommended approach, making NgModules optional. This represents a fundamental shift in application architecture.
• Environment Requirements:
  • Node.js: Support for older versions has been dropped. v13 requires Node.js 12.20+, v15 requires 14.20+, and v17 requires 18.13.0+.
  • TypeScript: The required version has been progressively updated. v11 added support for TypeScript 4.0, v13 for 4.4, and v15 for 4.8+.
• End of IE11 Support: Support for Internet Explorer 11 was officially dropped in Angular v13, allowing the framework to adopt modern browser features and reduce bundle sizes.
• New Control Flow Syntax: Angular v17 introduced a new, built-in control flow syntax (@if, @for) that replaces the previous structural directives (*ngIf, *ngFor).

Recommendation: A direct upgrade from v10 to v20 is not feasible. The official Angular documentation recommends a step-by-step migration, one major version at a time, using the ng update command. Start by migrating from 10 to 11, then 11 to 12, and so on, addressing the specific breaking changes for each version. This is a major refactoring effort that must be handled with significant planning and testing.

Source: Angular Update Guide

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