Skip to content

Releases: uNetworking/uWebSockets.js

v20.29.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 29 May 19:07

Obvious user error messages

This release tweaks the error messages given to users who use the library wrongly. Now they are less technical and more helpful and guides the user to the docs and manual:

On ill-use of uWS.HttpRequest:

Error: uWS.HttpRequest must not be accessed after await or route handler return. See documentation for uWS.HttpRequest and consult the user manual.

On ill-use of uWS.HttpResponse:

Warning: uWS.HttpResponse writes must be made from within a corked callback. See documentation for uWS.HttpResponse.cork and consult the user manual.

Hopefully users will stop reporting these errors as if they were bugs in uWS, and instead read them and go to the docs to solve the problem on their end.

v20.28.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 28 May 05:37
  • Updates uWS to v20.43.0

v20.27.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 28 May 00:35

Some corrections to last release. A better warning is now used:

Warning: uWS.HttpResponse writes must be made from within a corked callback. See documentation for uWS.HttpResponse.cork and consult the user manual.

Some fixes to TypeScript definitions have been merged.

v20.26.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 27 May 20:40

Warning of ill-use

This release adds something I have wanted to add for a long time. While the user manual is pretty clear on this, many users don't care to read it. So with this release there is now a in-your-face critical warning for ill-use regarding corking.

This release is backwards compatible, since we only issue warnings, but next major release will make this warning into a forceful termination of your app. This is done, to make it crystal clear that you aren't using uWS.js properly.

On invalid use, you will now get this:

Critical warning: Calling uWS.HttpResponse [.writeStatus, .writeHeader, .end, .write, .tryEnd, .upgrade, .endWithoutBody, or similar] outside of uWS.HttpResponse.cork callback is highly discouraged due to major performance loss! Read the user manual and make the fix.

If you get this warning, fix your app.

v20.25.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 19 May 18:12

Alien tech 👾

This release introduces a new mode of integration; no integration. Setting the environment variable ALIEN_UWS=1 makes uWS run entirely alien to Node.js, on its own separate event-loop. This mode greatly increases performance of uWS.js given the same CPU-time budget, by escaping Node.js's heavy weight AsyncHook feature that always imposes a huge performance penalty to your entire Node.js process, regardless if you actually use it or not. AsyncHook will not be able to track uWS.js callbacks in this mode.

uWebSockets js v20 25 0 msg_sec, with and without ALIEN_UWS=1 on Node js v20 2 0, Linux  CPU-time normalized

v20.24.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 01 May 18:21
  • Updates uWS to v20.40.0.

v20.23.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 21 Apr 18:17
  • Updates uWS to v20.39.0.

v20.22.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 20 Apr 17:05

Node.js LTS 16, 18, 20 support

  • Three latest LTS of Node.js supported.
  • Node.js 19 support removed.

v20.21.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 16 Apr 20:04
  • Updates uWS to v20.38.0

Full Changelog: v20.20.0...v20.21.0

v20.20.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 08 Mar 14:03
7029168

Full Changelog: v20.19.0...v20.20.0