pubnub - npm Package Versions

v8.8.1

February 10 2025

Fixed

• Fix issue because of which APM fix worked only when the client has been configured with logVerbosity: true.

v8.7.1

January 31 2025

Fixed

• Fix long-poll request cancellation caused by APM packages monkey patching 'fetch' and try to use 'native' implementation instead of patched.

v8.7.0

January 30 2025

Added

• Pass heartbeat request through SharedWorker (if used) to optimize the number of requests for clients opened in few tabs and subscribed on same channels / groups list.

Modified

• Don't send heartbeat request to unsubscribe.

v8.6.0

January 21 2025

Added

• A new optional parameter ifMatchesEtag is added to setUUIDMetadata and setChannelMetadata. When provided, the server compares the argument value with the ETag on the server and if they don't match a HTTP 412 error is returned.

v8.5.0

January 15 2025

Added

• Add fileRequestTimeout client configuration option which is specific only for requests which upload and download files.

Fixed

• Fix issue with instanceId set to undefined for requests with useInstanceId configuration flag set to true.

v8.4.1

January 02 2025

Fixed

• Fixed issue of hereNow response parsing for totalOccupancy field.

v8.4.0

December 17 2024

Added

• Add type field for members and membership objects and subscribe response.

Fixed

• Fixed type which limited number of options which can be included into response / used in sorting for members / membership setting API.
• Fix missing hereNowRefresh flag from the presence object received from subscribe.
• Fix issue because of which logVerbosity set to true still didn't print logs for Node.js.

Modified

• Change format and add proper request body output.

v8.3.2

December 12 2024

Fixed

• Fix issue with Subscription and SubscriptionSet when one can unsubscribe channel / group which is still in use by another.
• Fix particular TypeError emitted when browser forcefully closes long-poll connection before its timeout and reported as bad request. This type of error will be reported as a network error.
• Fix issue because of which node-fetch used default agent, which after Node.js 19+ has keepAlive enabled by default.

v8.3.1

November 18 2024

Fixed

• Fix issue because of which presence events not delivered to the Subscription and SubscriptionSet objects (only global listeners).