Sourced fromengine.io's releases.

6.4.1

This release contains6e78489, which exports theBaseServer class in order to restore the compatibility with thenodenext module resolution strategy of TypeScript.

Reference:https://www.typescriptlang.org/tsconfig/#moduleResolution

Related:socketio/socket.io#4621

Links

• Diff:socketio/engine.io@6.4.0...6.4.1
• Client release: -
• ws version:~8.11.0 (no change)

6.4.0

Features

• add support for Express middlewares (24786e7)

This commit implements middlewares at the Engine.IO level, because Socket.IO middlewares are meant for namespace authorization and are not executed during a classic HTTP request/response cycle.

A workaround was possible by using the allowRequest option and the "headers" event, but this feels way cleaner and works with upgrade requests too.

Syntax:

engine.use((req,res,next)=>{// do somethingnext();});// with express-sessionimportsessionfrom"express-session";engine.use(session({secret:"keyboard cat",resave:false,saveUninitialized:true,cookie:{secure:true}}));// with helmetimporthelmetfrom"helmet";engine.use(helmet());

Links

• Diff:socketio/engine.io@6.3.1...6.4.0

... (truncated)

Sourced fromengine.io's changelog.

6.4.1 (2023-02-20)

This release contains6e78489, which exports theBaseServer class in order to restore the compatibility with thenodenext module resolution strategy of TypeScript.

Reference:https://www.typescriptlang.org/tsconfig/#moduleResolution

Related:socketio/socket.io#4621

Dependencies

• ws@~8.11.0 (no change)

6.4.0 (2023-02-06)

Features

• add support for Express middlewares (24786e7)

This commit implements middlewares at the Engine.IO level, because Socket.IO middlewares are meant for namespace authorization and are not executed during a classic HTTP request/response cycle.

A workaround was possible by using the allowRequest option and the "headers" event, but this feels way cleaner and works with upgrade requests too.

Syntax:

engine.use((req,res,next)=>{// do somethingnext();});// with express-sessionimportsessionfrom"express-session";engine.use(session({secret:"keyboard cat",resave:false,saveUninitialized:true,cookie:{secure:true}}));// with helmetimporthelmetfrom"helmet";engine.use(helmet());

... (truncated)

• 7033c0e chore(release): 6.4.1
• 6e78489 refactor: export BaseServer class (#669)
• 535b068 docs: add upgrade event in the documentation
• 898bd1c chore(release): 6.4.0
• 6220d14 chore(deps): bump cookiejar from 2.1.2 to 2.1.4 (#667)
• 24786e7 feat: add support for Express middlewares
• 4d6f454 chore(release): 6.3.1
• 69603b9 refactor: make the compress option optional
• ae1ea77 chore(release): 6.3.0
• a65a047 fix: wait for all packets to be sent before closing the WebSocket connection
• Additional commits viewable incompare view

Sourced frombrowser-sync's releases.

The one that restores IE11 support 💪

What's Changed

• fix ie11 by@​shakyShane inBrowserSync/browser-sync#2024

esbuild does not support down-level transpiling as far as IE11 - so when I switched to it, it accidentally brokeIE11 support 😢

This is an important issue for me - many devs that support old browsers like IE11 are doing so because their projects are used in public services, or internal applications. Not every developer out there has the luxury of supporting evergreen-only browsers.

So, IE11 will work once again 🎉. Please use theissues thread to make me aware of any problem that's preventing you from using Browsersync in your day job 💪 (and be sure to thumbs-up the issues you want to see resolved)

# IE11 works, againnpm install browser-sync@latest

Full Changelog:BrowserSync/browser-sync@v2.28.3...v2.29.0

the one that finally removesdocument.write

What's Changed

• browser-sync-2017 use chalk everywhere by@​shakyShane inBrowserSync/browser-sync#2018
• fix: remove document.write by@​shakyShane inBrowserSync/browser-sync#2019

Full Changelog:BrowserSync/browser-sync@v2.27.12...v2.28.0

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

... (truncated)

• 6ffc212 v2.29.1
• 7b07798 v2.29.1-alpha.0
• 497f216 remove client deps
• bed04d4 v2.29.0
• 87421b5 fix: ie11 support (#2024)
• 59eb01a v2.28.3
• 3fd2720 v2.28.2
• 8487a85 bump logger (#2026)
• a841795 chalk as main dep - fixes#2021 (#2025)
• 9ea395f v2.28.1
• 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)
  You can disable automated security fix PRs for this repo from theSecurity Alerts page.