chore(deps): update dependency webext-bridge to v6 #949
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.0.5
->6.0.1
Release Notes
zikaari/webext-bridge (webext-bridge)
v6.0.1
Compare Source
v6.0.0
Compare Source
This revision is primarily focused on codebase improvements all around. The code should be now much
more readable and easy to comprehend as the responsibilities have been split into smaller pieces and
composed as needed by each runtime context.
For end users of the library, the breaking changes aren't that "breaking", they'll just need to do a
bit of import restructring. The API behaviour is mostly unchanged, with just minor exceptions.
Breaking changes
webext-bridge
. You must import the relevant part yourself depending on the context, eg:import Bridge from 'webext-bridge/window'
for a script that'll be running in the Window context. Learn more about the change here.
setNamespace
is not available in any context exceptwindow
, andallowWindowMessaging
is not available in any context exceptcontent-script
.getCurrentContext
export has been removed.isInternalEndpoint
returnstrue
for some new contexts. In summary it'll betrue
forbackground
,content-script
,devtools
,popup
, andoptions
.background
, message queuing feature can no longer be trusted due to manifest v3 terminating the service worker runtime after certain time. The queue of messagessent from
background
will be disposed off along with the termination of the said service worker. Queuing still works for messages sent from all other contexts.Fixes
content-script
orwindow
when being sent by some other context right after a tab had navigated forward or back. This was caused by old port'sonDisconnect
callback being called after the new port'sonConnect
callback. TheonDisconnect
would then remove the port mapping preventing messages from being routed tocontent-script
orwindow
.that's never coming back. Now, the
sendMessage
call in the sender will reject with an error.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.