Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new
threshold
option to control when compression is applied to WebSocket messages. Messages smaller than the threshold will skip compression entirely, which can improve performance by avoiding unnecessary compression overhead on small payloads.Key Changes
threshold
configuration option (defaults to 0 - always compress)Buffer.allocUnsafe
permessage-deflate2
to avoid conflictsWhy This Matters
Small messages often don't benefit from compression and can actually become larger due to compression overhead. By allowing users to set a minimum size threshold, we can:
Breaking Changes
permessage-deflate2
Usage