ci: electron example should not build with top level yarn build

[joker23]

Note

Low Risk
Low risk CI refactor plus removal of an example-only build script; main impact is on the GitHub Actions e2e job behavior and environment variable/secrets setup.

Overview
Refactors .github/workflows/electron.yaml’s run-example job to call the shared ./actions/run-example composite action instead of inlining dependency install/build, Xvfb/Playwright setup, and test execution.

Enhances actions/run-example/action.yml to support an env_vars input (written to $GITHUB_ENV) and to fetch the mobile SDK key in addition to the existing client-side and flag keys; the Electron workflow now supplies DISPLAY/ELECTRON_DISABLE_SANDBOX and moves Xvfb/Playwright/startup into before_test.

Removes the build script from packages/sdk/electron/example/package.json, so the example no longer exposes a top-level yarn build entry point.

^{Written by Cursor Bugbot for commit 7790739. This will update automatically on new commits. Configure here.}

---

[github-actions]

@launchdarkly/js-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 25566 bytes
Compressed size limit: 26000
Uncompressed size: 125383 bytes

[github-actions]

@launchdarkly/browser size report
This is the brotli compressed size of the ESM build.
Compressed size: 172527 bytes
Compressed size limit: 200000
Uncompressed size: 802217 bytes

[github-actions]

@launchdarkly/js-client-sdk size report
This is the brotli compressed size of the ESM build.
Compressed size: 24539 bytes
Compressed size limit: 25000
Uncompressed size: 85098 bytes

[github-actions]

@launchdarkly/js-client-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 22203 bytes
Compressed size limit: 24000
Uncompressed size: 115238 bytes

[joker23]

@cursor review

[joker23]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Double dash consumed by yarn, breaking electron build-exit

High Severity

The old build script was "electron-forge start -- --build", where the -- separator told electron-forge to pass --build through to the electron binary's process.argv. The new command yarn workspace @internal/electron-example start -- --build has yarn's CLI parser (Clipanion Option.Proxy()) consume the -- separator, resulting in electron-forge start --build without the --. Since --build is not a recognized electron-forge option, it likely won't reach process.argv, causing the process.argv.includes('--build') check in main.ts to fail. Instead of exiting immediately after building, the app would fully launch.

Additional Locations (1)

• packages/sdk/electron/example/package.json#L8-L9

 

[joker23]

this is actually exactly what I want it to do.