@cloudcrane/app-runtime 0.3.0 → 0.6.0

package/README.md

@@ -12,7 +12,7 @@ const { html, sha256, runtime } = compile(spec);
 ```
 
 - `compile(spec)` returns the page, its sha256 and the runtime it was built
-  with (`@cloudcrane/app-runtime@0.2.0+<hash>`); it throws `CompileError`
+  with (`@cloudcrane/app-runtime@0.4.0+<hash>`); it throws `CompileError`
   listing every problem when the spec doesn't validate.
 - `compile(spec, { runtime: "shared" })` links the runtime instead of inlining
   it: the page names `runtimeFile().path` (`/_cc/runtime/<version>-<hash>.js`)
@@ -39,6 +39,20 @@ const { html, sha256, runtime } = compile(spec);
   game.random(); // seeded by the page
   ```
 
+  The page kit runs an HTML page as it is, full screen. Its `localStorage`
+  works: what it holds is written into the frame when it opens, and each
+  change goes to the page, which keeps it under `<data.key>.coded.<id>` (at
+  most 4 MB), so it survives a reload and an update and the frame sees only
+  its own. Both kits reach the page through `window.__ccBus`.
+
+  A component's frame is allowed the device features the spec's `uses`
+  declares (its `allow`), and the page must allow them for frames too (in
+  Permissions-Policy, `geolocation=*` rather than `(self)`). Browsers give a
+  frame with no origin of its own no camera or microphone, so a page kit whose
+  spec declares either runs with the page's origin; it's then no more apart
+  from the page than an app written straight into it. A game kit always
+  stays apart.
+
 - `@cloudcrane/app-runtime/host`: what a host publishing spec apps needs in one
   import (validate, compile, derive the blueprint).
 

package/dist/compiler/compile.d.ts

@@ -13,6 +13,7 @@ export type LinkedRuntime = {
     path: string;
     integrity: string;
 };
+/** `runtime` names the runtime the page carries, or is "page" for an HTML app's spec, which is its page as written, with none. */
 export type Compiled = {
     html: string;
     sha256: string;

package/dist/compiler/compile.js

@@ -1,5 +1,5 @@
 import { createHash } from "node:crypto";
-import { canonical, validateSpec } from "@cloudcrane/app-spec";
+import { canonical, pageOf, validateSpec } from "@cloudcrane/app-spec";
 import { CODED_CSS, DATESTRIP_CSS } from "../runtime/styles.js";
 import { tokensCss } from "../runtime/theme.js";
 import { RUNTIME_JS, RUNTIME_SHA256, RUNTIME_VERSION } from "./runtime.generated.js";
@@ -40,13 +40,18 @@ export function compile(input, options = {}) {
     const { spec, problems } = validateSpec(input);
     if (!spec)
         throw new CompileError(problems);
+    // A spec that is an HTML app's page is that page, as written: no runtime, so any runtime version builds it the same.
+    const page = pageOf(spec);
+    if (page !== null)
+        return { html: page, sha256: createHash("sha256").update(page).digest("hex"), runtime: "page" };
     if (spec.manifest.runtime !== RUNTIME_VERSION)
         throw new CompileError([{ at: "manifest.runtime", problem: `this compiler builds runtime ${RUNTIME_VERSION}` }]);
     // Only what drawing the app needs goes in the page: not the journeys, promises or tests.
-    // Coded components go in only when there are some.
+    // Coded components go in only when there are some, and the device features they may use only when it uses some.
     const inPage = {
         module: spec.module,
         ...(Object.keys(spec.components).length ? { components: spec.components } : {}),
+        ...(spec.uses.length ? { uses: spec.uses } : {}),
         data: spec.data,
         logic: spec.logic,
         surface: spec.surface,