[NEUTRAL] Update dependency pusher-js to v8 #811
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 contains the following updates:
^5.1.1
->^8.0.0
Release Notes
pusher/pusher-js (pusher-js)
v8.3.0
Compare Source
v8.2.0
Compare Source
v8.1.0
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
v7.6.0
Compare Source
v7.5.0
Compare Source
v7.4.1
Compare Source
v7.4.0
Compare Source
v7.3.0
Compare Source
v7.2.0
Compare Source
v7.0.6
Compare Source
v7.0.5
Compare Source
allows it to be bundled as described in the README
v7.0.4
Compare Source
v7.0.3
Compare Source
[UPDATED] Bumped version of faye-websocket (used only by the node runtime) from
0.9.4 to 0.11.3. Thanks to @Akhawais for the PR.
[UPDATED] Bumped version of @react-native-community/netinfo (used only by the
react-native runtime) from 4.1.1 to 5.9.7. Thanks to @Yinabled for the PR.
[ADDED] We were missing a react-native key in
package.json
. Thanks to @giasetfor the PR
[ADDED] Support for importing the worker builds (solving issue #499)
v7.0.2
Compare Source
[FIXED] Removes
AuthInfo
type from react-native and with-encryption builds.This type was removed everywhere else in v7.0.0. See issue
512
v7.0.1
Compare Source
[FIXED] Channels no longer get stuck in the
subscriptionPending
stateafter a failed request to an auth endpoint. Fixes Issue
255
v7.0.0
Compare Source
[UPDATED] Type signatures for authorizer callback. Previously the authorizer
callback had 2 arguments, the first was a boolean indicating that the second
was an error. Switched for a more conventional
function(err, data)
signature.This is a breaking change, if you use a custom authorizer
[UPDATED] Types of errors emitted on
pusher:subscription_error
events.Previously this event just contained the status code the auth endpoint
returned. This was replaced with a (hopefully) more error object with a message
and a
status
key.This is a breaking change, if you depend on the status in the
pusher:subscription_error
event[FIXED] Stop wrapping websocket errors multiple times. Fixes issue
464
This might be a breaking change, if you depend on the structure of
'error'
eventsemitted by
pusher.connection
[FIXED] Stop swallowing errors thrown by handlers on encrypted channels.
Previously errors thrown by handlers bound to encrypted channels were caught
and ignored. This was unintentional and undesirable. Fixes Issue
437
v6.0.3
Compare Source
[FIXED] Added typescript declarations for the pusher-js/with-encryption build
[REMOVED] Unnecessary dummy tweetnacl types for react-native (thanks to
@dmitrybirin)
[UPDATED] Copyright years (thanks to @annzenkina)
v6.0.2
Compare Source
[FIXED] React-native import broken in release 6.0.1
v6.0.1
Compare Source
[CHANGED] Moved tweetnacl from
devDependencies
todependencies
. Noadditional code is included in the bundle, but this gives the typescript
compiler access to the tweetnacl types
[FIXED] Typescript declarations for react-native. These were supposed to be
included in 6.0.0 but the commit was missed
v6.0.0
Compare Source
[CHANGED] The default builds for web and worker no longer support encrypted
channels. To use encrypted channels in web/worker you must import
pusher-js/with-encryption
or use thepusher-with-encryption.js
/pusher-with-encryption.min.js
bundles[CHANGED]
forceTLS
now defaults totrue
[REMOVED] the
encrypted
option - this was deprecated in4.3.0
. The librarydefaults to TLS anyway. Setting
encrypted
tofalse
will NOT changebehaviour
[FIXED]
activityTimeout
andpongTimeout
options now work as described inthe docs.
[NEW] Typescript declarations for react-native
[NEW] Support for encrypted-channels in react-native and workers
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.