@crossworks/app-build 0.232.153 → 0.232.165

package/package.json

@@ -1,22 +1,23 @@
 {
   "name": "@crossworks/app-build",
-  "version": "0.232.153",
+  "version": "0.232.165",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",
   "exports": {
     ".": "./src/index.ts"
   },
+  "files": [
+    "src"
+  ],
   "dependencies": {
-    "@mantle/share-ui": "npm:@crossworks/share-ui@0.232.153",
+    "@mantle/share-ui": "npm:@crossworks/share-ui@0.232.165",
     "@tailwindcss/oxide": "^4.3.3",
     "esbuild": "^0.28.1",
     "lucide-react": "^1.25.0",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
-    "tailwindcss": "^4.3.3",
-    "@mantle/config": "0.0.1",
-    "@mantle/std": "0.0.1"
+    "tailwindcss": "^4.3.3"
   },
   "devDependencies": {
     "@types/node": "^26.4.0",

package/src/index.ts

@@ -15,7 +15,13 @@ import { fileURLToPath } from 'node:url';
 import esbuild, { type BuildOptions, type Message, type Plugin } from 'esbuild';
 import { buildAppCss } from './css';
 import { KIT } from './kit';
-import { errorMessage } from '@mantle/std';
+// Local copy of @mantle/std's errorMessage. This package is published as a
+// contract package; it must not depend on private workspace packages, which
+// do not exist on npm (the v0.232.122-153 tarballs shipped an unresolvable
+// @mantle/std@0.0.1 dependency for exactly this import).
+function errorMessage(err: unknown): string {
+  return err instanceof Error ? err.message : String(err);
+}
 
 /** Specifiers provided by the shared runtime via the iframe import map — marked
  *  external so they stay as bare imports in the app bundle. The react family is

package/src/runtime-exports.ts

@@ -24,13 +24,16 @@
 import { readFile } from 'node:fs/promises';
 import * as path from 'node:path';
 import { fileURLToPath } from 'node:url';
-import { env } from '@mantle/config';
 
 const HERE = path.dirname(fileURLToPath(import.meta.url));
 
 /** In order of trust: explicit override, package-relative, cwd convention. */
 export function manifestCandidates(): string[] {
-  const override = env('MANTLE_APP_RUNTIME_MANIFEST');
+  // Raw read on purpose: this package is published to npm and cannot depend
+  // on the private @mantle/config package. The name stays in config's
+  // inventory so it is documented alongside every other variable.
+  // eslint-disable-next-line no-restricted-syntax
+  const override = process.env.MANTLE_APP_RUNTIME_MANIFEST;
   return [
     ...(override ? [override] : []),
     // packages/app-build/src → <root>/server/web/public/app-runtime/manifest.json

package/scripts/build-runtime.ts

@@ -1,61 +0,0 @@
-/**
- * Emits the shared mini-app runtime into an app's `public/app-runtime/`.
- * Run with: `node packages/app-build/scripts/build-runtime.ts` from the app
- * directory (Node strips the TS types). Invoked from `predev`/`prebuild` in
- * server/web and in jackdaw's client/web, so the runtime always exists before
- * apps render.
- */
-import { existsSync } from 'node:fs';
-import * as path from 'node:path';
-import { buildRuntime } from '../src/build-runtime.ts';
-import { env } from '@mantle/config';
-
-/**
- * Where to write. Each Next app serves its own copy — the ACAO:* runtime has
- * to exist on every origin that renders sandboxes.
- *
- * Paths resolve from the CALLER'S CWD, never from this script's own location.
- * They used to resolve against `../../..` from here, which is the repo root
- * only while this package sits in the repo being built. Published to npm and
- * installed by the jackdaw repo, that same expression pointed at the
- * consumer's `node_modules/`, so `build-runtime.ts client/web` wrote the
- * runtime to `node_modules/client/web/public/app-runtime` — a real directory
- * nothing serves. The owner UI shipped with NO `/app-runtime/*` at all (its
- * Docker build runs the same prebuild), and nothing failed: the build printed
- * a success line naming the wrong path, and only a sandboxed mini-app trying
- * to boot would notice.
- *
- * An ARGUMENT rather than an environment variable, deliberately. The callers
- * used to set `APP_RUNTIME_OUT="$PWD/…"` inline, which is POSIX shell syntax;
- * pnpm runs package scripts through cmd.exe on Windows, where that is not a
- * variable assignment but an unknown command. The desktop build failed on
- * windows-latest for four consecutive releases with
- * `'APP_RUNTIME_OUT' is not recognized`. An argv entry has no shell semantics
- * to get wrong.
- *
- * `APP_RUNTIME_OUT` still works for a direct absolute-path invocation.
- */
-const appArg = process.argv[2]?.trim();
-const appDir = path.resolve(process.cwd(), appArg ?? '.');
-const outDir = env('APP_RUNTIME_OUT')
-  ? path.resolve(env('APP_RUNTIME_OUT'))
-  : path.join(appDir, 'public/app-runtime');
-
-// Tripwire for the failure above: a Next app always has a `public/`, so its
-// absence means the resolved app directory is not an app and the runtime is
-// about to be written somewhere nothing serves. Fail loudly here rather than
-// print a cheerful success line pointing into node_modules. Skipped when
-// APP_RUNTIME_OUT names the destination outright.
-if (!env('APP_RUNTIME_OUT') && !existsSync(path.join(appDir, 'public'))) {
-  console.error(
-    `app-runtime: ${appDir} has no public/ directory, so it is not an app.\n` +
-      `Run this from the app directory (paths resolve from the cwd), or pass an ` +
-      `absolute destination as APP_RUNTIME_OUT.`,
-  );
-  process.exit(1);
-}
-
-const manifest = await buildRuntime(outDir);
-const n = Object.keys(manifest.imports).length;
-console.log(`app-runtime: ${n} modules → ${outDir}`);
-for (const [spec, url] of Object.entries(manifest.imports)) console.log(`  ${spec}  →  ${url}`);

package/tsconfig.json

@@ -1,14 +0,0 @@
-{
-  "extends": "../../tsconfig.base.json",
-  "compilerOptions": {
-    "rootDir": "src",
-    "outDir": "dist",
-    "types": ["node"],
-    // build-runtime.ts is executed directly by Node (the build:runtime script),
-    // which requires explicit `.ts` import specifiers. This package is only ever
-    // typechecked (--noEmit) or transpiled by Next, never emitted by tsc — so
-    // allowing the extension keeps the Node-run and tsc paths in agreement.
-    "allowImportingTsExtensions": true
-  },
-  "include": ["src/**/*.ts"]
-}