mirror of
https://github.com/element-hq/element-call.git
synced 2026-10-06 05:57:16 +00:00
Set up `sdk/` as a package shaped exactly like `component/`: its own package.json with peer dependencies, the pnpm workspace marker so a host can install it as a git dependency, a build tsconfig for type emission, and a vite lib config with an externals list that `pnpm lint:externals` now checks for both library builds. The package holds only the interface for now. `createRtcSession` returns an empty object; `RtcSession`, `RtcMember`, `MemberMedia` and `TransportMetadata` are the contract Element Call's `CallViewModel` will be rebuilt on (see sdk-plan.md). The shared primitives are re-exported from `src` until the first implementation slice moves them. `sdk/dev` is the smallest consumer of the SDK: a plain page that logs in, joins a room and renders one tile per member, served by `pnpm dev:sdk` on port 3002. Playwright starts it as a third web server, and `playwright/sdk/smoke.spec.ts` has two browsers join one session. It fails on the status line with the SDK's own error until there is an implementation behind the interface. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Element Call Docs
This folder contains documentation for setup, usage, and development of Element Call.
- Embedded vs standalone mode
- Element Call as a React component (experimental)
- Url format and parameters
- Global JS controls
- MatrixRTC modes
- Self-Hosting
- Developing with linked packages
Writing code for Element Call (agent-readable conventions)
Entry point: AGENTS.md.