toDOM pulls in lib.dom.ts types in TSC - incompatible with server-side environments

[vlovich]

Checklist

[ ] Are you reporting a bug? Use github issues for bug reports and feature requests. For general questions, please use https://discuss.yjs.dev/ [ ] Try to report your issue in the correct repository. Yjs consists of many modules. When in doubt, report it to https://github.com/yjs/yjs/issues/

Is your feature request related to a problem? Please describe. Compiling a TypeScript project that depends on TSC currently pulls in the DOM types & breaks any project targetting a non-browser environment (e.g. Cloudflare Workers & probably Deno).

Describe the solution you'd like The toDOM (& querySelector?) would be moved to a separate set of typings that the user has to explicitly pull in? Maybe some other option? I'm not familiar with what an ideal solution would look like.

Describe alternatives you've considered For now I'm using patch-package to omit the offending methods.

Additional context TSC config:

{
  "compilerOptions": {
    "target": "esnext",
    "lib": ["esnext"],
    "alwaysStrict": true,
    "strict": true,
    "noEmitOnError": true,
    "moduleResolution": "node",
    "outDir": "tscOutDir",
    "preserveConstEnums": true,
    "esModuleInterop": true,
    "types": ["@cloudflare/workers-types", "jest"]
  },
  "lib": ["esnext"],
  "exclude": ["node_modules"]
}

@cloudflare/workers-types is not compatible with dom.d.ts & dom.d.ts wouldn't be the correct types for things like WebSocket (in Cloudflare Workers Response lets you access the returned WebSocket).

_{Huly®: YJS-291}

[dmonad]

Hi @vlovich,

the next major release v14.0.0 will not contain toDom methods anymore.

I can't remove these typings right now without breaking compatibility. Hope you found a workaround.