Upgrade an existing app
From SDK 4.x to 4.6
npm install @w3booster/sdk@4.6.0
npm run check
npm run build
Protocol remains 4.0. Existing lifecycle, settings and transport APIs continue
to work. New statistics are optional; keep rendering useful views when a field is
absent. Import /analytics only if your app needs retained match history.
SDK 4.5.1 and earlier rejected new attributes inside POIs. Upgrade apps requesting
pois:read for this rollout. SDK 4.6 fixes that validator and preserves safe optional
attributes through snapshots, patches and local recorder state. This does not
retroactively fix older bundled SDKs.
From 4.6, future optional state additions must not require your app to upgrade. Known types, required fields and closed enums still form a contract: changing those needs an explicit version transition. See the compatibility policy.
Only run npm run w3booster:sync if your app definition changes. A package upgrade
or newly delivered optional state field does not itself change your definition.
If you add a new requested scope, update the app definition, sync, rebuild and test
a fresh authorized launch.
Verify the experience before publishing
- Start the app with demo data; test no match, missing values and reconnect UI.
- Open Test locally through W3Booster for real data and granted scopes.
- Check self-play and observer/replay separately. Never infer a winner from exit.
- Check transparent overlays, menus, resize and any interactive regions.
- Test the installed desktop as well as a modern browser. Electron 15 uses Chromium 94.
- Deploy HTML and assets together, then open a fresh launch. Keep previous assets available while an older page can still reference them.
From earlier major versions
Use the SDK 4 migration guide for removed aliases, protocol changes, scoped native state and catalog joins. Review publishing for app registration and hosting rather than copying old launch URLs or credentials.