branch-video-player-sdk 0.2.13 → 0.2.15

package/README.md

@@ -39,6 +39,27 @@ Subscribe with `player.on()` to `loaded`, `ready`, `statechange`, `progress`,
 `ended`, `error`, `bufferchange`, `milestone`, and `exitrequested`. `play`,
 `pause`, and `seek` issued before trusted `ready` are queued in order.
 
+## Runtime size and boot overlay (0.2.15+)
+
+Until 0.2.14 the Runtime bundle `assets/player-*.js` weighed 10.8 MB because
+theme artwork (about 9 MB of base64 PNG/SVG) was inlined into the JavaScript.
+On a 250 KB/s connection the first frame stayed on a fake "0% 0B / 0B" for
+more than 40 seconds before `script.json` was even requested.
+
+- Images larger than 4 KB are now emitted as `assets/img-<hash>.<ext>` and
+  referenced relative to `player.html`, which keeps working for every host
+  layout (npm package, H5 copy, static image) because `player.html` and
+  `assets/` are always siblings. The bundle is about 1.2 MB (365 KB gzip).
+- `player.html` no longer shows a fake percentage before the module runs. It
+  says the player itself is loading, counts the seconds, warns after 15 s and
+  offers a retry after 60 s. The React overlay with real resource progress
+  takes over as before.
+- The runtime build fails if any JS/CSS still contains an inlined image over
+  4 KB or if total JS exceeds 3 MB (`scripts/validate-runtime-artifacts.mjs`).
+
+Hosts should serve `assets/**` with long-lived immutable caching and gzip; the
+file names are content-hashed.
+
 ## Web learning observations (0.2.10+)
 
 The Runtime can report privacy-minimized Web learning observations through the existing `milestone` event. These observations are included in 0.2.10 and later; 0.2.9 does not contain them. No new SDK event name is required.