@rebon/cli-win32-x64 1.2.0 → 1.4.0

package/payload/compose-runtime/src/payload.mjs

@@ -1,49 +1,49 @@
-// Where the vendored JS payload lives.
-//
-// The payload — Cordis, cosmokit, schemastery and the dsh package set — is this
-// package's own, in `payload/`. It used to be owned by `crates/rebon-kernel-js`
-// and pointed at from here, because the deno_core host was what shipped and two
-// copies of a 600KB vendored tree would diverge. V8 is gone, so the tree moved
-// next to its runtime and this file is the only one that changed.
-//
-// `vendor/cordis/index.js` is the sentinel, for the same reason `bridge.js`
-// is on the Rust side: every consumer loads it, so a directory without it is
-// not a payload.
-import fs from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const SENTINEL = path.join('vendor', 'cordis', 'index.js');
-const here = path.dirname(fileURLToPath(import.meta.url));
-
-const holdsPayload = (dir) => fs.existsSync(path.join(dir, SENTINEL));
-
-/// The payload directory, or a refusal naming what was tried.
-///
-/// A ladder, not a search — the same rule `REBON_PLUGIN_NODE` follows on the
-/// Rust side. `REBON_KERNEL_JS_DIR` is an explicit demand: if what it names
-/// does not hold a payload, that is the answer, not a reason to go looking
-/// somewhere else. Falling back would run the composition against a payload
-/// the operator did not choose and never told them.
-///
-/// Without the override there is one place it can be: `payload/` inside this
-/// package, in a checkout and in a deployment alike.
-///
-/// Throws rather than returning a guess, because every module specifier the
-/// composition resolves is built from this path — a wrong one surfaces later
-/// as two dozen unrelated "cannot find module" errors.
-export function payloadDir() {
-  const override = process.env.REBON_KERNEL_JS_DIR;
-  if (override) {
-    if (holdsPayload(override)) return path.resolve(override);
-    throw new Error(
-      `[NO_PAYLOAD] REBON_KERNEL_JS_DIR names ${override}, which does not hold ${SENTINEL}`,
-    );
-  }
-  const beside = path.join(here, '..', 'payload');
-  if (holdsPayload(beside)) return path.resolve(beside);
-  throw new Error(
-    `[NO_PAYLOAD] no vendored JS payload found (looked for ${SENTINEL} under ${beside}); `
-      + 'set REBON_KERNEL_JS_DIR to the directory holding it',
-  );
-}
+// Where the vendored JS payload lives.
+//
+// The payload — Cordis, cosmokit, schemastery and the dsh package set — is this
+// package's own, in `payload/`. It used to be owned by `crates/rebon-kernel-js`
+// and pointed at from here, because the deno_core host was what shipped and two
+// copies of a 600KB vendored tree would diverge. V8 is gone, so the tree moved
+// next to its runtime and this file is the only one that changed.
+//
+// `vendor/cordis/index.js` is the sentinel, for the same reason `bridge.js`
+// is on the Rust side: every consumer loads it, so a directory without it is
+// not a payload.
+import fs from 'node:fs';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const SENTINEL = path.join('vendor', 'cordis', 'index.js');
+const here = path.dirname(fileURLToPath(import.meta.url));
+
+const holdsPayload = (dir) => fs.existsSync(path.join(dir, SENTINEL));
+
+/// The payload directory, or a refusal naming what was tried.
+///
+/// A ladder, not a search — the same rule `REBON_PLUGIN_NODE` follows on the
+/// Rust side. `REBON_KERNEL_JS_DIR` is an explicit demand: if what it names
+/// does not hold a payload, that is the answer, not a reason to go looking
+/// somewhere else. Falling back would run the composition against a payload
+/// the operator did not choose and never told them.
+///
+/// Without the override there is one place it can be: `payload/` inside this
+/// package, in a checkout and in a deployment alike.
+///
+/// Throws rather than returning a guess, because every module specifier the
+/// composition resolves is built from this path — a wrong one surfaces later
+/// as two dozen unrelated "cannot find module" errors.
+export function payloadDir() {
+  const override = process.env.REBON_KERNEL_JS_DIR;
+  if (override) {
+    if (holdsPayload(override)) return path.resolve(override);
+    throw new Error(
+      `[NO_PAYLOAD] REBON_KERNEL_JS_DIR names ${override}, which does not hold ${SENTINEL}`,
+    );
+  }
+  const beside = path.join(here, '..', 'payload');
+  if (holdsPayload(beside)) return path.resolve(beside);
+  throw new Error(
+    `[NO_PAYLOAD] no vendored JS payload found (looked for ${SENTINEL} under ${beside}); `
+      + 'set REBON_KERNEL_JS_DIR to the directory holding it',
+  );
+}

package/payload/compose-runtime/src/plugin.mjs

@@ -1,59 +1,59 @@
-// The composition control plugin.
-//
-// rebon loads this one first, and everything else the composition contains is
-// loaded after it, as an ordinary `plugin/load` each. What this one does is
-// make that possible: install module resolution for the vendored payload,
-// create the shared Cordis realm the entries mount into, and answer for the
-// facts the protocol has no field for.
-//
-// **Why the structure lives in this plugin's config.** Groups and `isolate` are
-// composition structure, not plugin facts: a group is a container that is not a
-// module, and an isolated realm is a relationship between entries. Neither can
-// be said in one entry's own load request, so rebon says it once, here, naming
-// only ids and placement. Each entry's `plugin/load` then carries its module
-// and its own configuration.
-//
-// Module resolution has to be installed before Cordis is imported, and static
-// imports are linked before a module body runs — which is why everything below
-// is imported dynamically. Only Node's own builtins, which need no resolution,
-// could be static, and none are needed.
-export async function activate(api, config = {}) {
-  const { installModuleResolution } = await import('./resolve.mjs');
-  installModuleResolution({
-    ...(config.payloadDir ? { dir: config.payloadDir } : {}),
-    extraModules: config.modules ?? {},
-  });
-
-  const { withCall } = await import('./bridge.mjs');
-  const { builtinSeats, createRealm, mounted, reportFor } = await import('./realm.mjs');
-  await createRealm({ web: config.web ?? null, entries: config.entries ?? [] });
-
-  // Registered before any entry is loaded, so an entry claiming the same
-  // service name hits the registrar's refusal rather than replacing this.
-  //
-  // What it answers is the part of a load report the protocol cannot carry: a
-  // route's model catalog, a prompt section, a web provider. Those belong to
-  // one plugin kind, and the ready report is a shape every plugin shares — so
-  // they are asked for rather than bolted on.
-  api.service('compose', async (request, ctx) => withCall(ctx, async () => {
-    const kind = request?.kind;
-    if (kind === 'list') {
-      return { plugins: mounted(), builtin: builtinSeats() };
-    }
-    if (kind === 'report') {
-      const pluginId = String(request?.pluginId ?? '');
-      const report = reportFor(pluginId);
-      if (report === undefined) {
-        const error = new Error(`no composition entry ${JSON.stringify(pluginId)} is mounted`);
-        error.code = '[UNKNOWN_PLUGIN]';
-        throw error;
-      }
-      return report;
-    }
-    const error = new Error(`compose does not answer kind ${JSON.stringify(kind ?? null)}`);
-    error.code = '[UNKNOWN_CONTROL]';
-    throw error;
-  }));
-}
-
-export default activate;
+// The composition control plugin.
+//
+// rebon loads this one first, and everything else the composition contains is
+// loaded after it, as an ordinary `plugin/load` each. What this one does is
+// make that possible: install module resolution for the vendored payload,
+// create the shared Cordis realm the entries mount into, and answer for the
+// facts the protocol has no field for.
+//
+// **Why the structure lives in this plugin's config.** Groups and `isolate` are
+// composition structure, not plugin facts: a group is a container that is not a
+// module, and an isolated realm is a relationship between entries. Neither can
+// be said in one entry's own load request, so rebon says it once, here, naming
+// only ids and placement. Each entry's `plugin/load` then carries its module
+// and its own configuration.
+//
+// Module resolution has to be installed before Cordis is imported, and static
+// imports are linked before a module body runs — which is why everything below
+// is imported dynamically. Only Node's own builtins, which need no resolution,
+// could be static, and none are needed.
+export async function activate(api, config = {}) {
+  const { installModuleResolution } = await import('./resolve.mjs');
+  installModuleResolution({
+    ...(config.payloadDir ? { dir: config.payloadDir } : {}),
+    extraModules: config.modules ?? {},
+  });
+
+  const { withCall } = await import('./bridge.mjs');
+  const { builtinSeats, createRealm, mounted, reportFor } = await import('./realm.mjs');
+  await createRealm({ web: config.web ?? null, entries: config.entries ?? [] });
+
+  // Registered before any entry is loaded, so an entry claiming the same
+  // service name hits the registrar's refusal rather than replacing this.
+  //
+  // What it answers is the part of a load report the protocol cannot carry: a
+  // route's model catalog, a prompt section, a web provider. Those belong to
+  // one plugin kind, and the ready report is a shape every plugin shares — so
+  // they are asked for rather than bolted on.
+  api.service('compose', async (request, ctx) => withCall(ctx, async () => {
+    const kind = request?.kind;
+    if (kind === 'list') {
+      return { plugins: mounted(), builtin: builtinSeats() };
+    }
+    if (kind === 'report') {
+      const pluginId = String(request?.pluginId ?? '');
+      const report = reportFor(pluginId);
+      if (report === undefined) {
+        const error = new Error(`no composition entry ${JSON.stringify(pluginId)} is mounted`);
+        error.code = '[UNKNOWN_PLUGIN]';
+        throw error;
+      }
+      return report;
+    }
+    const error = new Error(`compose does not answer kind ${JSON.stringify(kind ?? null)}`);
+    error.code = '[UNKNOWN_CONTROL]';
+    throw error;
+  }));
+}
+
+export default activate;