Archived

This repository has been archived on 2026-05-05. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

T

History

Will Anderson d1ec384b27 rename crates/ to engrams/, bindings/ to receptors/

- crates/ → engrams/ (Rust engrams live here)
- bindings/ → receptors/ (cross-language access points into the graph)
- Cargo.toml workspace paths updated

2026-04-29 03:27:33 -05:00

src

rename crates/ to engrams/, bindings/ to receptors/

2026-04-29 03:27:33 -05:00

Cargo.toml

rename crates/ to engrams/, bindings/ to receptors/

2026-04-29 03:27:33 -05:00

package.json

rename crates/ to engrams/, bindings/ to receptors/

2026-04-29 03:27:33 -05:00

README.md

rename crates/ to engrams/, bindings/ to receptors/

2026-04-29 03:27:33 -05:00

tsconfig.json

rename crates/ to engrams/, bindings/ to receptors/

2026-04-29 03:27:33 -05:00

README.md

TypeScript Bindings (planned v0.2)

Two paths for TypeScript/Node.js:

Option A — WASM (browser + Node)

cargo build --target wasm32-unknown-unknown --release -p engram-core
wasm-bindgen target/wasm32-unknown-unknown/release/engram_core.wasm --out-dir pkg/

Requires wasm-bindgen annotations on public API. Browser-compatible, no native deps.

Option B — Node native addon (server-side)

Use napi-rs to generate a Node.js native addon from engram-core. Faster than WASM for server-side agents, but requires a native build step per platform.

Status

Stub only. WASM target is the preferred path for v0.2 given the local-first, embedded philosophy.