@arcadible/sdk 1.0.0 → 1.1.0

package/README.md

@@ -46,7 +46,7 @@ const progress = saved ? JSON.parse(saved) : { level: 1 };
 await arcadible.saves.write("progress", JSON.stringify(progress));
 ```
 
-A save is a name holding one string. `ready` settles once the game's saves have loaded, and never fails; from then on, `readSync` answers from memory. Every call that fails rejects with an `ArcadibleError`, whose `code` says what to do.
+A save is a name holding one string. `ready` settles once the game's saves have loaded, and never fails; from then on, `readSync` answers from memory. Every call that fails rejects (or, for `readSync`, throws) with an `ArcadibleError`, whose `code` says what to do.
 
 Off Arcadible, such as on your dev server, the package works on its own, with the same rules and limits: saves are kept on the page's own origin, and `arcadible.build` is `null`.
 

package/dist/bus/protocol.js

@@ -9,22 +9,19 @@ export const BUS_VERSION = 1;
 export const HANDSHAKE_TIMEOUT = 1000;
 // How long a request waits for its response.
 export const REQUEST_TIMEOUT = 10_000;
-// The play pages a game accepts a welcome from: production's, and `arc
-// serve`'s on this machine. Another development page (play.arcadible.test)
-// is passed with `createClient({ origins })`, never trusted by what games
-// ship, since a hostile network could pose as an http one.
-const HOST_ORIGINS = ["https://play.arcadible.com"];
-// `arc serve`'s play page, on any port. The network can't pose as loopback,
-// and on Arcadible a build's `frame-ancestors` lets only the play page frame
-// it, so no local page can reach a player's saves there.
-const LOCAL_ORIGIN = /^http:\/\/localhost:\d+$/u;
 // [function]
 // Whether a game accepts a welcome from `origin`: one of `origins` when it
-// was given, or else production's or `arc serve`'s.
+// was given (tests, and development pages), or else any real origin, `http`
+// included, whatever framed it. Who may frame a build is decided outside the
+// game, where it can change: on Arcadible by each build's `frame-ancestors`,
+// which the browser enforces before the game runs, and elsewhere by whoever
+// serves it. So the host is never trusted with anything of value (DESIGN.md,
+// section 4). Only `null` is refused: a `file://` page or a sandboxed frame,
+// which can't be told apart.
 export function isHostOrigin(origin, origins) {
     return origins
         ? origins.includes(origin)
-        : HOST_ORIGINS.includes(origin) || LOCAL_ORIGIN.test(origin);
+        : origin !== "null" && origin !== "";
 }
 // The most requests one game can have waiting on the page; past it, a
 // request fails with `busy`.

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const VERSION = "1.0.0";
+export declare const VERSION = "1.1.0";

package/dist/version.js

@@ -1,3 +1,3 @@
 // The client's version, sent in its hello and shown as `arcadible.version`,
 // for bug reports. It matches package.json (test/unit/protocol.test.ts).
-export const VERSION = "1.0.0";
+export const VERSION = "1.1.0";

package/package.json

@@ -43,5 +43,5 @@
   ],
   "type": "module",
   "types": "./dist/index.d.ts",
-  "version": "1.0.0"
+  "version": "1.1.0"
 }