-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support embedding of the Element Call assets within a widget host #2994
Labels
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
Comments
This was referenced Feb 6, 2025
Merged
Merged
Work in progress is visible at livekit...hughns:element-call:publishing |
hughns
added a commit
to hughns/element-call
that referenced
this issue
Mar 10, 2025
fetch returns a response code of 0 when it successfully loads a `file://` resource. This means we can't just rely on `response.ok`. Required for element-hq#2994
This was referenced Mar 10, 2025
hughns
added a commit
that referenced
this issue
Mar 11, 2025
fetch returns a response code of 0 when it successfully loads a `file://` resource. This means we can't just rely on `response.ok`. Required for #2994
hughns
added a commit
to hughns/element-call
that referenced
this issue
Mar 11, 2025
fetch returns a response code of 0 when it successfully loads a `file://` resource. This means we can't just rely on `response.ok`. Required for element-hq#2994
hughns
added a commit
to hughns/element-call
that referenced
this issue
Mar 11, 2025
Part of element-hq#2994 This creates a new "embedded" build (vs "full" build) at the vite level. It will be used by a later PR that actually provides platform specific packages. Embedded build: - Uses relative URLs - Uses relative config.json path and other resource loading - Has a config.json built in - Doesn't include the public folder (e.g. favicon) Out of scope: - this doesn't attempt to exclude SPA functionality, so technically the build could be used in SPA - the above means that the crypto-wasm binary is included in the build
hughns
added a commit
to hughns/element-call
that referenced
this issue
Mar 12, 2025
Part of element-hq#2994 This creates a new "embedded" build (vs "full" build) at the vite level. It will be used by a later PR that actually provides platform specific packages. Embedded build: - Uses relative URLs - Uses relative config.json path and other resource loading - Has a config.json built in - Doesn't include the public folder (e.g. favicon) Out of scope: - this doesn't attempt to exclude SPA functionality, so technically the build could be used in SPA - the above means that the crypto-wasm binary is included in the build
This was referenced Mar 12, 2025
hughns
added a commit
that referenced
this issue
Mar 12, 2025
* Embedded package build of Element Call Part of #2994 This creates a new "embedded" build (vs "full" build) at the vite level. It will be used by a later PR that actually provides platform specific packages. Embedded build: - Uses relative URLs - Uses relative config.json path and other resource loading - Has a config.json built in - Doesn't include the public folder (e.g. favicon) Out of scope: - this doesn't attempt to exclude SPA functionality, so technically the build could be used in SPA - the above means that the crypto-wasm binary is included in the build * CI artifact name based on type of build * Update src/config/Config.ts
hughns
added a commit
to hughns/element-call
that referenced
this issue
Mar 12, 2025
Part of element-hq#2994 This PR: - Publishes embedded builds as Tarball, NPM, AAR, SwiftPM for releases - Publishes full builds as Tarball for releases - Adds comments to release notes with the built artifact locations
hughns
added a commit
that referenced
this issue
Mar 12, 2025
Part of #2994 This PR: - Publishes embedded builds as Tarball, NPM, AAR, SwiftPM for releases - Publishes full builds as Tarball for releases - Adds comments to release notes with the built artifact locations
This was referenced Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
This only needs to support Element Call running as a widget (not standalone).
Specific scenarios that we want to support:
Pull requests:
The text was updated successfully, but these errors were encountered: