mengw15 commented on issue #6210: URL: https://github.com/apache/texera/issues/6210#issuecomment-4895794840
**Deferring — `@y/websocket-server` isn't production-ready yet.** The package is currently on **unreleased yjs v14 prereleases with a broken dependency graph**. A fresh `npm install` of `@y/[email protected]` (what the Dockerfile does) resolves: ``` @y/[email protected] ├─ [email protected] # server Doc (import * as Y from 'yjs') └─ @y/[email protected] └─ @y/[email protected] # sync protocol ``` `yjs` and `@y/y` are two packages at **drifted** v14 prerelease points, so the server throws on every update: ``` TypeError: store.getClock is not a function ``` The floating `"yjs": "^14.0.0-7"` drifts to `14.0.0-16`, which no longer matches the `@y/[email protected]` that `@y/protocols` locks — regenerating the lockfile just pins the broken combination. On top of that, yjs `latest` is still **v13.6.31** (v14 is `next`/`beta` only) and the frontend client is on **yjs 13.5.41**, so this would also put a v14 server against v13 clients. A pinned `overrides` workaround (alias `yjs` → `@y/y`) makes it run, but on unreleased yjs v14 and tripping Yjs's `already imported … will lead to issues` double-load guard — not worth it for a production real-time service. **Decision:** stay on `[email protected]` (stable yjs v13, matches the client) until `@y/websocket-server` ships stable on stable yjs v14, ideally upgrading the frontend client in the same change. Closing as deferred. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
