Skip to content

Releases: uNetworking/uWebSockets.js

v20.39.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 08 Jan 22:38

Bumps uWS to v20.56.0

v20.38.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 24 Dec 00:54

Bumps uWS to v20.53.0

v20.37.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 23 Dec 15:34
0fce132

Bumps uWS to v20.52.0

v20.36.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 23 Dec 02:30
2fc43d4
  • Fixes broken v20.35.0

image

v20.35.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 21 Dec 07:56
  • Bumps uWS to v20.51.0
  • Adds new .dropped event

v20.34.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 09 Nov 22:12
fca27c0

Bumps uWS to v20.48.0

v20.33.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 22 Oct 19:26

Node.js 21

Apparently the idea of only supporting LTS versions of Node.js went down the shitter. New rule will be:

  • 3 most recent LTS versions (or to be LTS) are supported.
  • Latest non-LTS (never to become) supported until replaced with a new one.

This means Node.js 16, 18, 20 and 21 are supported now.

Then it becomes 18, 20, 21, 22.
Then it becomes 18, 20, 22, 23.
Then it becomes 20, 22, 23, 24.
Then it becomes 20, 22, 24, 25.

Then, you should really just swap to Bun.

v20.32.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 24 Sep 23:32

Fixes

  • Updates uWS to v20.47.0

v20.31.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 15 Jul 18:40

HTTP error pages

This release bumps uWS to v20.45.0 which adds error codes / pages for:

  • 505
  • 431
  • 400
  • 404

This means easier debugging when using proxies, as uWS won't simply respond with a generic RST (which often ends up as a 502 in the proxy), but will instead return proper HTTP error pages / status codes that can be handled & logged properly.

v20.30.0

Choose a tag to compare

@uNetworkingAB uNetworkingAB released this 30 May 01:15

More user error message fixes

This release reverts v20.25.0 since it was quickly found to be a heavily misunderstood and misused mode. This change is backwards compatible, as the flag will simply be ignored.

This release also tweaks the onWritable error message into a warning message that better guides the user to a solution:

Warning: uWS.HttpResponse.onWritable callback should return Boolean. See documentation for uWS.HttpResponse.onWritable and consult the user manual.

It also tweaks the error message from use of deleted uWS.HttpResponse:

Error: uWS.HttpResponse must not be accessed after uWS.HttpResponse.onAborted callback, or after a successful response. See documentation for uWS.HttpResponse and consult the user manual.