[Snyk] Fix for 2 vulnerabilities

[saumilmac]

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
• frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Handling of Length Parameter Inconsistency SNYK-JS-WEBSOCKETDRIVER-17987994	746
	Allocation of Resources Without Limits or Throttling SNYK-JS-WS-17988732	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

[saumilmac]

This multi-package upgrade introduces significant breaking changes across both @angular-devkit/build-angular and socket.io-client, requiring major code and configuration updates. Both upgrades are considered high risk.

@angular-devkit/build-angular@0.1000.8 → @angular-devkit/build-angular@13.0.0

This is a major upgrade spanning three Angular versions (v10 to v13). It includes several critical breaking changes:

• View Engine Removed: As of v13, the legacy View Engine is no longer available. All libraries and application code must be Ivy-compatible. Projects still using View Engine will fail to compile.
• Internet Explorer 11 Support Dropped: Support for IE11 was removed in Angular v13.
• Node.js Requirement: Support for Node.js versions older than v12.20.0 has been dropped.
• Build Configuration: The structure of angular.json and build options have changed. The versioning scheme of this package was also aligned with Angular's main version, and the underlying build tooling has been updated.

Recommendation: This upgrade cannot be performed in a single step. Developers must follow the official Angular Update Guide to migrate incrementally from v10 through v11, v12, and finally to v13.

socket.io-client@2.4.0 → socket.io-client@4.8.0

This upgrade crosses two major versions (v2 → v3 → v4) and contains severe breaking changes, primarily in the v2 to v3 transition.

• Protocol Incompatibility: A socket.io-client v3+ is not compatible with a v2 server. The server and all clients must be upgraded simultaneously. While a v4 server can communicate with a v2 client if configured with allowEIO3: true, a v3/v4 client cannot connect to a v2 server.
• API Redesign (Client-Side):
  • Reconnection logic events (e.g., reconnect_attempt) are no longer emitted on the socket instance. Listeners must be moved to the manager instance (socket.io).
  • The query connection option was renamed to auth.
  • Several methods and properties were removed or changed, such as io.set() and Socket.use().

Recommendation: This upgrade requires a coordinated deployment of both the server and all clients. Review the official migration guides for v2 to v3 and [v3 to v4](https://socket.

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