Kevin Jahns
Kevin Jahns
This looks pretty pretty dangerous, considering that we have an incompatible beta release running too. ``` "y-js": "*", ``` Can you check which version is actually installed?
And I'm really sorry for the late answer .. I didn't see the issue and just stumbled on it..
@Horusiath
Good catch @zackzhou-work So this is about Yjs and Y-CRDT producing different output. Ideally, they are identical, but there might be small differences. You found one. @Horusiath Just noticed this....
The idea of the `status` event is to tell the user about the connection status. Hence, I'd prefer to add a status event `{ status: 'disconnecting', reason: 'timeout' | 'manual'...
The server moved to yjs/y-websocket-server. It is a proper ESM module now with typings.
Hi @lukebayes, Unfortunately, simple-peer is the best battle-proven webrtc solution out there. But feel free to investigate if there are alternatives with a smaller footprint, I'd be intrigued as well.
Alright, closing. But please feel free to reopen if you find alternatives.
This looks pretty cool. Thanks for sharing @neftaly! I might accept a PR to switch to tiny-simple-peer. My only concern is whether this package works as reliably (well, as reliable...
To me, the following would be more familiar: ```js const observer = yVal.observe( () => { // do something }) onUnmount(()=>{ yVal.unobserve(observer) }) ``` I like that the observer is...