@metta-ts/node and @metta-ts/browser

The two platform entry points. Both re-export everything from @metta-ts/core and add platform-specific pieces.

@metta-ts/node

npm install @metta-ts/node          # library
npm install -g @metta-ts/node       # the metta-ts CLI on your PATH

CLI

metta-ts path/to/program.metta
npx -p @metta-ts/node metta-ts path/to/program.metta   # without a global install

Runs a .metta file, resolving import! relative to the file's directory, and prints each !-query's results.

API

function runFile(path: string, fuel?: number): QueryResult[]
function readImports(src: string, baseDir: string): Map<string, Atom[]>
class ParallelFlatMatcher {
  constructor(kb: FlatKB, workerCount?: number);
  match(pattern: Atom): Promise<Array<Map<string, Atom>>>;   // variable name -> atom, per match
  close(): Promise<void>;                                     // terminate the worker pool
}

runFile runs a file from disk. readImports pre-reads the import! targets a program references, resolving names against baseDir. ParallelFlatMatcher scans a FlatKB across worker_threads over a SharedArrayBuffer; build it once, reuse the warm pool, and close() when done. It is for large, non-selective, small-result scans only (see scaling).

@metta-ts/browser

npm install @metta-ts/browser

function run(src: string, files?: Map<string, string>, fuel?: number): QueryResult[]
function vfsImports(src: string, files: Map<string, string>): Map<string, Atom[]>

run evaluates a program in the browser, resolving import! against an in-memory virtual file system (files maps a module name to its MeTTa source). vfsImports builds that import map directly. The whole interpreter is pure TypeScript, so it runs in any browser with no native addon and no WASM, which is exactly what powers the playground.