[Snyk] Fix for 2 vulnerabilities

[icsnyk]

Snyk has created this PR to fix 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	170
	Directory Traversal SNYK-JS-TAR-15307072	165

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal

[icsnyk]

This upgrade spans multiple major versions of the Angular toolchain (CLI, Build, and Custom Webpack) from v15 to v18+, introducing significant and mandatory breaking changes. The most critical impact is the architectural shift in Angular's build system, which directly conflicts with the use of @angular-builders/custom-webpack.

Top Breaking Changes:

• Build System Overhaul & custom-webpack:

  • Angular v17 introduced a new default build system powered by esbuild and Vite (using the application builder in angular.json). This replaces the previous webpack-based system (browser builder).
  • @angular-builders/custom-webpack is designed to customize the legacy webpack build. Migrating to the new application builder is incompatible with custom-webpack's primary function.
  • Action Required: You must make a strategic decision: either stick with the legacy webpack builder to continue using your custom configurations or migrate to the new application builder and find alternative solutions for your build customizations.

• Node.js & TypeScript Requirements:

  • The required Node.js version has been raised significantly. Angular v18 requires Node.js ^18.19.1 or ^20.11.1 or higher.
  • The required TypeScript version is now ~5.4.

• Removal of Angular Compatibility Compiler (ngcc):

  • As of Angular v16, ngcc has been completely removed. This means any third-party libraries that are not compiled with the Ivy rendering engine are no longer supported and will break your build.

• New Control Flow and Standalone APIs:

  • Angular v17 introduced a new built-in control flow syntax (@if, @for) which is now recommended over *ngIf and *ngFor.
  • Standalone components are the default for new projects since v17.

Recommendation:

Due to the number of breaking changes, a direct jump is not recommended. Follow the official Angular Update Guide step-by-step for each

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

[snyk-io]

✅ 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
✅	Code Security	0	0	0	0	0 issues

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