@mosetta/cli 0.0.9 → 0.0.11

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # @mosetta/cli
 
+## 0.0.11
+
+### Patch Changes
+
+- Updated dependencies [eea103d]
+  - @mosetta/runtime@0.0.11
+  - @mosetta/build@0.0.11
+  - @mosetta/server@0.0.11
+  - @mosetta/stores@0.0.11
+
+## 0.0.10
+
+### Patch Changes
+
+- 95b93d5: The build's node host is an entry of the build: `@mosetta/build/node` gives the real file system,
+  the framework's files resolved from the installed build, and `buildDirectory(root, …)` — the build
+  of a palette that lies on disk with its dependencies installed, by the build installed for it. The
+  CLI builds with it, and so does a platform's build container: a palette is built by the framework
+  version its lock names. `systemjs`, whose files the build mixes into a page, is a dependency of the
+  build now, not of the CLI.
+- Updated dependencies [95b93d5]
+  - @mosetta/build@0.0.10
+  - @mosetta/stores@0.0.10
+  - @mosetta/runtime@0.0.10
+  - @mosetta/server@0.0.10
+
 ## 0.0.9
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosetta/cli",
-  "version": "0.0.9",
+  "version": "0.0.11",
   "license": "MIT",
   "description": "mosetta CLI: development server (single port, live reload, type-check companion), building a deployable tile palette and publishing it.",
   "type": "module",
@@ -13,10 +13,10 @@
     "esbuild-wasm": "0.24.2",
     "systemjs": "^6.15.1",
     "workerd": "^1.20260630.1",
-    "@mosetta/build": "0.0.9",
-    "@mosetta/runtime": "0.0.9",
-    "@mosetta/server": "0.0.9",
-    "@mosetta/stores": "0.0.9"
+    "@mosetta/build": "0.0.11",
+    "@mosetta/stores": "0.0.11",
+    "@mosetta/runtime": "0.0.11",
+    "@mosetta/server": "0.0.11"
   },
   "publishConfig": {
     "access": "public"

package/src/host/nodeFileSystem.mjs

@@ -1,45 +1,3 @@
-import fs from 'node:fs';
-import { FileSystem } from '@mosetta/build/fileSystem';
-
-/**
- * Node implementation of the file port: the real FS, read-only.
- *
- * Resolution no longer lives here: `createRequire` contexts died together with the `resolve`
- * method — packages are resolved by `PackagesResolver` from the scanner catalog, identically in
- * all environments.
- */
-export class NodeFileSystem extends FileSystem {
-  readFile(file, encoding = null) {
-    return encoding ? fs.readFileSync(file, encoding) : fs.readFileSync(file);
-  }
-
-  exists(file) {
-    return fs.existsSync(file);
-  }
-
-  readDir(dir) {
-    return fs.readdirSync(dir, { withFileTypes: true })
-      .map((e) => ({ name: e.name, isDirectory: e.isDirectory() }));
-  }
-
-  isDirectory(dir) {
-    try {
-      return fs.statSync(dir).isDirectory();
-    } catch {
-      return false;
-    }
-  }
-
-  realPath(file) {
-    return fs.realpathSync(file);
-  }
-
-  mtimeMs(file) {
-    try {
-      return fs.statSync(file).mtimeMs;
-    } catch {
-      return null;
-    }
-  }
-
-}
+// The node file port lives with the build's node host (@mosetta/build/node), shared with the
+// platform's build container; kept here under its old path for the CLI's own imports.
+export { NodeFileSystem } from '@mosetta/build/node';

package/src/scanner.mjs

@@ -1,26 +1,6 @@
-import { createRequire } from 'node:module';
-import { FRAMEWORK_RESOLUTIONS } from '@mosetta/build/packagesResolver';
-
-/**
- * The node side of the scanner: ONLY framework resolutions — files from the CLI's own
- * installation (systemjs etc. — its dependencies) that the build mixes in by itself.
- *
- * The package-catalog scanner itself is portable and lives in `@mosetta/build/scanner`: it
- * takes the file port and uses only sources and pnpm-lock.yaml from it — exactly what the
- * scanner isolate will have. Only `createRequire` remains here, because resolving the tool's
- * installation is an environment capability; in the isolate a pre-seeded map in the plan
- * replaces it.
- */
-const cliRequire = createRequire(import.meta.url);
-
-/** File for a framework specifier from the CLI installation (for frameworkDir in harnesses). */
-export function frameworkFileOf(specifier) {
-  return cliRequire.resolve(specifier);
-}
-
-/** `catalog.framework`: ready answers for the FRAMEWORK_RESOLUTIONS list. */
-export function frameworkResolutions() {
-  const framework = {};
-  for (const spec of FRAMEWORK_RESOLUTIONS) framework[spec] = cliRequire.resolve(spec);
-  return framework;
-}
+// The node side of the scanner — ONLY framework resolutions: the files the build mixes in by
+// itself (systemjs, the runtime's bootstrap), resolved from the installation of @mosetta/build —
+// the build's node host (@mosetta/build/node), which the platform's build container uses too.
+//
+// The package-catalog scanner itself is portable and lives in `@mosetta/build/scanner`.
+export { frameworkFileOf, frameworkResolutions } from '@mosetta/build/node';