Closed mifopen closed 2 years ago
I'm sorry, I don't understand this bug report. How do I reproduce this? lib0 is already a dependency of y-websocket and I don't think it makes sense to add it as a peerDependency.
Ah, so I guess you mean to bump lib0 because the broadcastchannel has a new feature that doesn't exist in the older versions of lib0. Yeah I can do that.
Looks like you need to set
lib0
peerDependency to at least0.2.51
. Otherwise, passingprovider
asorigin
parameter ofpublish
function doesn't make any effect and messages are handled by the "origin" instance as well. As a result,the "origin" instance handles the final awareness update on destroying/disconnecting the provider and thus holding itself in the "on" state for others on reconnection :)Huly®: YJS-529