Sourced fromengine.io's releases.

6.2.1

⚠️ This release contains an important security fix⚠️

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)Emitted 'error' event on Socket instance at:    at emitErrorNT (internal/streams/destroy.js:106:8)    at emitErrorCloseNT (internal/streams/destroy.js:74:3)    at processTicksAndRejections (internal/process/task_queues.js:80:21) {  errno: -104,  code: 'ECONNRESET',  syscall: 'read'}

Please upgrade as soon as possible.

Bug Fixes

• catch errors when destroying invalid upgrades (#658) (425e833)

6.2.0

Features

• add the "maxPayload" field in the handshake details (088dcb4)

So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSizevalue.

This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), aswe only add a field in the JSON-encoded handshake data:

0{"sid":"lv_VI97HAXpY6yYWAAAC","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000,"maxPayload":1000000}

Links

• Diff:socketio/engine.io@6.1.3...6.2.0
• Client release:6.2.0
• ws version:~8.2.3

6.1.3

Bug Fixes

• typings: allow CorsOptionsDelegate as cors options (#641) (a463d26)
• uws: properly handle chunked content (#642) (3367440)

... (truncated)

Sourced fromengine.io's changelog.

6.2.1 (2022-11-20)

⚠️ This release contains an important security fix⚠️

A malicious client could send a specially crafted HTTP request, triggering an uncaught exception and killing the Node.js process:

Error: read ECONNRESET    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)Emitted 'error' event on Socket instance at:    at emitErrorNT (internal/streams/destroy.js:106:8)    at emitErrorCloseNT (internal/streams/destroy.js:74:3)    at processTicksAndRejections (internal/process/task_queues.js:80:21) {  errno: -104,  code: 'ECONNRESET',  syscall: 'read'}

Please upgrade as soon as possible.

Bug Fixes

• catch errors when destroying invalid upgrades (#658) (425e833)

3.6.0 (2022-06-06)

Bug Fixes

• add extension in the package.json main entry (#608) (3ad0567)
• do not reset the ping timer after upgrade (1f5d469), closessocketio/socket.io-client-swift#1309

Features

• decrease the default value of maxHttpBufferSize (58e274c)

This change reduces the default value from 100 mb to a more sane 1 mb.

This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

See also:GHSA-j4f2-536g-r55m

• increase the default value of pingTimeout (f55a79a)

... (truncated)

• 24b847b chore(release): 6.2.1
• 425e833 fix: catch errors when destroying invalid upgrades (#658)
• 99adb00 chore(deps): bump xmlhttprequest-ssl and engine.io-client in /examples/latenc...
• d196f6a chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#660)
• 7c1270f chore(deps): bump nanoid from 3.1.25 to 3.3.1 (#659)
• 535a01d ci: add Node.js 18 in the test matrix
• 1b71a6f docs: remove "Vanilla JS" highlight from README (#656)
• 917d1d2 refactor: replace deprecatedString.prototype.substr() (#646)
• 020801a chore: add changelog for version 3.6.0
• ed1d6f9 test: make test script work on Windows (#643)
• Additional commits viewable incompare view

Sourced frombrowser-sync's releases.

2.27.9

What's Changed

• fix(cli): Where's the command help? fixes#1929 by@​shakyShane inBrowserSync/browser-sync#1945

A bug prevented the help output from displaying - it was introduced when the CLI parseryargs was updated, and is now fixed :)

Full Changelog:BrowserSync/browser-sync@v2.27.8...v2.27.9

2.27.8

This release upgrades Socket.io (client+server) to the latest versions - solving the following issues, and silencing security warning :)

PR:

• BrowserSync/browser-sync@58ab4ab

Resolved Issues:

• BrowserSync/browser-sync#1850
• BrowserSync/browser-sync#1892
• BrowserSync/browser-sync#1925
• BrowserSync/browser-sync#1926
• BrowserSync/browser-sync#1933

Thanks to@​lachieh for the original PR, which helped me land this fix

addedsnippet: boolean option

This release adds a feature to addressBrowserSync/browser-sync#1882

Sometimes you don't want Browsersync to auto-inject it's connection snippet into your HTML - now you can disable it globally via either a CLI param or the newsnippet option :)

browser-sync. --no-snippet

or in any Browsersync configuration

constconfig={snippet:false,};

the original request was related to Eleventy usage, so here's how that would look

eleventyConfig.setBrowserSyncConfig({snippet:false,});

... (truncated)

• f6965a6 v2.27.10
• e6c7bed Updated portscanner to 2.2.0 (#1960)
• 6a587ec fix readme's
• 91258ae Merge branch 'browser-sync-1946-esbuild'
• f48d6b4 👋 app veyor
• 30c24dc Merge pull request#1947
• 9d24de5 drop webpack from UI
• 7a00341 build client with esbuild
• c30868a v2.27.9
• 9b5fcdc fix(cli): Where's the command help? fixes#1929 (#1945)
• Additional commits viewable incompare view

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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from theSecurity Alerts page.