Commit Graph

9 Commits

Author SHA1 Message Date
fkwp
3d47609cff Since we are now using templating anyhow we can also combine full and embedded build into one step 2025-06-10 18:17:16 +02:00
fkwp
31185ae365 make build_mode optional 2025-06-06 00:13:49 +02:00
fkwp
97d548ee3a add build_mode input and use it in run commands 2025-06-05 23:51:02 +02:00
renovate[bot]
da2ce68348 Update GitHub Actions 2025-05-15 23:01:56 +00:00
renovate[bot]
e7086ff8fc Pin dependencies 2025-04-01 02:20:37 +00:00
Robin
31fb916b9d Enable CI to use Yarn Berry 2025-03-14 03:23:37 -04:00
Hugh Nimmo-Smith
7aac56aac0 Vite embedded build of Element Call (#3077)
* Embedded package build of Element Call

Part of https://github.com/element-hq/element-call/issues/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
2025-03-12 17:00:44 +00:00
renovate[bot]
8aa95d1ddd Update GitHub Actions 2025-03-03 15:54:20 +00:00
Hugh Nimmo-Smith
e23d8828ad GitHub Action workflows cannot be in a sub folder 2025-02-06 12:55:28 +00:00