[Snyk] Security upgrade ws from 6.2.5 to 8.21.1

[dceejay]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• hardware/sensehatsim/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Allocation of Resources Without Limits or Throttling SNYK-JS-WS-17988732

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

[dceejay]

This is a major version upgrade from v6 to v8, which includes significant breaking changes across two major versions (v7 and v8).

Breaking Changes in v7.0.0

• Node.js Support: Support for Node.js versions below 10.0.0 has been dropped.
• Message Size Limit: The maxPayload option now defaults to 100 MiB (104,857,600 bytes). Messages larger than this will be rejected.
• Connection Behavior: Sending a message during the connection phase (before 'open' is emitted) or after the connection is closed will now throw an error. Previously, it would be silently ignored.

Breaking Changes in v8.0.0

• Node.js Support: Support for Node.js versions below 12.0.0 has been dropped.
• Subprotocol Handling: The protocol option in the WebSocket constructor and the protocols option in the WebSocketServer constructor now only accept an array of strings. A single string is no longer supported and will throw a SyntaxError.

Recommendation:

• Verify that your Node.js runtime is v12.0.0 or higher.
• Review code to ensure that messages are not sent before the 'open' event or after the 'close' event.
• If using subprotocols, ensure the protocol or protocols options are passed as an array of strings.
• Confirm that your application does not rely on sending WebSocket messages larger than 100 MiB, or configure the maxPayload option accordingly.

Source: GitHub Releases

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

[linux-foundation-easycla]

• ❌ - login: @snyk-bot / name: snyk-bot. The commit (ee3aafb) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.