docs: EC fork now on upstream v0.25.0 — Node 24 / pnpm 11 / oxlint toolchain
Records the toolchain decisions taken with the 2026-09 upstream sync of LotusGuild/element-call (accept upstream: pnpm 11 + Node >= 22.13, oxlint/oxfmt replacing eslint/prettier, matrix-js-sdk develop pin), the tag-driven publish flow, and the pending 0.25.0-lotus.1 bundle. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA
This commit is contained in:
@@ -196,7 +196,7 @@ The dev server defaults to **port 8080** (`vite.config.js`); if 8080 is already
|
||||
### 🔱 Element Call fork ("Lotus Call") — LIVE
|
||||
|
||||
Voice/video channels embed **Element Call**, which is now our **self-built fork**
|
||||
(`@lotusguild/element-call-embedded` `0.20.1-lotus.1`, source at
|
||||
(`@lotusguild/element-call-embedded` `0.20.1-lotus.1`; `0.25.0-lotus.1` is built and tagged on the fork, pending publish — source at
|
||||
`LotusGuild/element-call`), published to our private Gitea npm registry and served
|
||||
same-origin. We no longer depend on the upstream prebuilt bundle, so in-call
|
||||
behavior is editable source instead of fragile DOM/widget hacks.
|
||||
|
||||
Reference in New Issue
Block a user