#69683be052 Thanks @niukanen1! - Add an isProd option to the ws, uWebSockets.js and @fastify/websocket use-server helpers, matching the existing crossws option. It controls whether internal error messages are masked with Internal server error before reaching the client, defaulting to the NODE_ENV === 'production' check as before. This lets apps running in production keep reporting onConnect error messages to the client by opting out, or mask eagerly in non-production environments.
Patch Changes
#700d8aeda6 Thanks @kratam! - Fix the client closing an in-use socket when many subscriptions complete at once and a new one subscribes within the lazyCloseTimeout
Every completing subscription scheduled its own lazy close timeout, but only the last one got cleared on the next connect. The client now keeps a single lazy close timeout and checks for active subscriptions before closing.
#7021e05c8c Thanks @Meemaw! - Avoid an unhandled rejection when a subscription is disposed before the connection is acknowledged and the socket closes before the subscription releases its connection lock (for example, when the client is disposed while connecting and the WebSocket implementation delivers the close event on a microtask).
Configuration
📅Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [graphql-ws](https://the-guild.dev/graphql/ws) ([source](https://github.com/enisdenjo/graphql-ws)) | [`6.3.0` → `6.4.0`](https://renovatebot.com/diffs/npm/graphql-ws/6.3.0/6.4.0) |  |  |
---
### Release Notes
<details>
<summary>enisdenjo/graphql-ws (graphql-ws)</summary>
### [`v6.4.0`](https://github.com/enisdenjo/graphql-ws/blob/HEAD/CHANGELOG.md#640)
[Compare Source](https://github.com/enisdenjo/graphql-ws/compare/v6.3.0...v6.4.0)
##### Minor Changes
- [#​696](https://github.com/enisdenjo/graphql-ws/pull/696) [`83be052`](https://github.com/enisdenjo/graphql-ws/commit/83be0521d510e3d53ee61288fda0f57dcfee78af) Thanks [@​niukanen1](https://github.com/niukanen1)! - Add an `isProd` option to the `ws`, `uWebSockets.js` and `@fastify/websocket` use-server helpers, matching the existing `crossws` option. It controls whether internal error messages are masked with `Internal server error` before reaching the client, defaulting to the `NODE_ENV === 'production'` check as before. This lets apps running in production keep reporting `onConnect` error messages to the client by opting out, or mask eagerly in non-production environments.
##### Patch Changes
- [#​700](https://github.com/enisdenjo/graphql-ws/pull/700) [`d8aeda6`](https://github.com/enisdenjo/graphql-ws/commit/d8aeda6504268e8b6a74e49c128393b9617a0ed5) Thanks [@​kratam](https://github.com/kratam)! - Fix the client closing an in-use socket when many subscriptions complete at once and a new one subscribes within the `lazyCloseTimeout`
Every completing subscription scheduled its own lazy close timeout, but only the last one got cleared on the next connect. The client now keeps a single lazy close timeout and checks for active subscriptions before closing.
- [#​702](https://github.com/enisdenjo/graphql-ws/pull/702) [`1e05c8c`](https://github.com/enisdenjo/graphql-ws/commit/1e05c8c2e6701d006b0e09c849dfadc234a79f4c) Thanks [@​Meemaw](https://github.com/Meemaw)! - Avoid an unhandled rejection when a subscription is disposed before the connection is acknowledged and the socket closes before the subscription releases its connection lock (for example, when the client is disposed while connecting and the WebSocket implementation delivers the close event on a microtask).
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNTUuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE1NS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
6.3.0→6.4.0Release Notes
enisdenjo/graphql-ws (graphql-ws)
v6.4.0Compare Source
Minor Changes
83be052Thanks @niukanen1! - Add anisProdoption to thews,uWebSockets.jsand@fastify/websocketuse-server helpers, matching the existingcrosswsoption. It controls whether internal error messages are masked withInternal server errorbefore reaching the client, defaulting to theNODE_ENV === 'production'check as before. This lets apps running in production keep reportingonConnecterror messages to the client by opting out, or mask eagerly in non-production environments.Patch Changes
#700
d8aeda6Thanks @kratam! - Fix the client closing an in-use socket when many subscriptions complete at once and a new one subscribes within thelazyCloseTimeoutEvery completing subscription scheduled its own lazy close timeout, but only the last one got cleared on the next connect. The client now keeps a single lazy close timeout and checks for active subscriptions before closing.
#702
1e05c8cThanks @Meemaw! - Avoid an unhandled rejection when a subscription is disposed before the connection is acknowledged and the socket closes before the subscription releases its connection lock (for example, when the client is disposed while connecting and the WebSocket implementation delivers the close event on a microtask).Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.