@missing-elements/h5p-offline-player 0.1.0 → 0.1.1

package/README.md

@@ -1,5 +1,8 @@
 # @missing-elements/h5p-offline-player
 
+[![npm](https://img.shields.io/npm/v/%40missing-elements%2Fh5p-offline-player)](https://www.npmjs.com/package/@missing-elements/h5p-offline-player)
+[![licence](https://img.shields.io/npm/l/%40missing-elements%2Fh5p-offline-player)](LICENSE)
+
 > **Not production ready.** This is an early release under active development. The API, the
 > worker protocol and the cache layout can still change between versions, and the browser
 > coverage is Chromium first. Try it, report what breaks, but do not put it in front of learners
@@ -22,10 +25,6 @@ The player is three things: the element (`h5p-player.js`, an ES module), a Servi
 has to be served from **your own origin**, because browsers refuse to register a worker from
 anywhere else. The other two can come from your bundle or from a CDN.
 
-> The package is being published to npm. Until it lands, build it from source: `git clone`,
-> `npm install`, `npm run build`, and serve `dist/` where the snippets below say the package's
-> files go.
-
 **A · With a bundler** (Vite, webpack 5, Rollup):
 
 ```bash
@@ -85,7 +84,9 @@ reads the archive in place and answers the H5P runtime's requests out of it:
 - the archive's **central directory** is read over HTTP `Range` requests, so a 300 MB package
   costs a few kilobytes before it starts;
 - **large spans are pulled by several connections at once** and reassembled in order, because a
-  single connection is often capped well below the link;
+  single connection is often capped well below the link — the first one streams straight into
+  the inflate, and the others open once it flows, so a slow link still sees its first bytes
+  within a second or two;
 - **small entries and scripts** are inflated once into a Cache API store;
 - **large stored media** is sliced straight out of the archive — never extracted, never stored;
 - **large deflated media** is inflated into 8 MB chunks by a page-side worker, and served
@@ -212,7 +213,7 @@ Properties: `src`, `file` (a `File` from a picker — setting it loads), `pkgId`
 | `progress` | Download or extraction progress, `fraction` 0–1 (or `null` when the total is unknown) |
 | `resize` | The content's height changed |
 | `statechange` | `state` changed |
-| `error` | `code`: `no-cors`, `no-worker`, `network`, `quota`, `bad-archive`, `runtime` |
+| `error` | `code`: `no-cors`, `no-worker`, `network`, `quota`, `bad-archive`, `runtime`. A `runtime` error after `ready` leaves `state` at `ready`: the content threw but is still running |
 
 ```js
 const player = document.querySelector('h5p-player')
@@ -234,6 +235,10 @@ no "open in another browser" banner. Those belong to the host page, built out of
 - `h5p-sw.js` is served from the site's own origin — browsers reject cross-origin Service Worker
   registration. With a bundler this is automatic. Frame assets may come from a CDN.
 - Package URLs send CORS headers. `Range` support is optional but avoids a full download first.
+- Storage is optional on a host that honours `Range`, and for a file picked from disk: the
+  player caches what fits and serves the rest straight from the archive. A host without `Range`
+  makes it a requirement — the whole archive has to be stored — and a package larger than the
+  room the browser gives the site is refused with `error: quota`, naming the size it needed.
 
 Integration details, including bundler-specific setup and single-worker hosts, are in
 [h5p-player-setup.md](h5p-player-setup.md). The design is in

package/dist/VERSION

@@ -1 +1 @@
-0.1.0
+0.1.1

package/dist/frame-assets/MANIFEST.json

@@ -1,4 +1,4 @@
 {
   "h5pStandalone": "3.8.2",
-  "player": "0.1.0"
+  "player": "0.1.1"
 }