@shapeshift-labs/frontier-framework

v0.1.4

Published

10 days ago

High-level Frontier framework package with config, CLI, Vite builds, monorepo scaffolding, sync transport contracts, split deploy artifacts, and evidence manifests.

0High
0Medium
0Low

shapeshift-labs

@shapeshift-labs/frontier-framework

frontier-framework is the high-level app package for building Frontier applications with a Next/SvelteKit-like developer surface while preserving Frontier package boundaries.

It provides:

frontier init for a monorepo scaffold with apps/web, apps/api, and packages/contracts.
Vite as the default frontend bundler path, with Frontier DOM TSX route compilation.
frontier build for separate frontend, backend, and evidence artifacts.
frontier.config.mjs as the app configuration contract.
TSX route authoring through @shapeshift-labs/frontier-dom JSX syntax.
Filesystem route discovery for page.tsx, +page.tsx, index.tsx, route.tsx, route groups, flat route files, private/excluded files, dynamic params, optional params, and splats.
Optional Vite hot module reloading through vite.hmr, defaulting to true.
Backend-neutral Fetch handler and transport contracts instead of a built-in backend framework.
Structural sync support for CRDT, realtime WebSocket, event-log, state-cache, worker, and custom adapters.
First-class runtime data-source migrations through @shapeshift-labs/frontier-migrations, with generated app-state/query-cache/CRDT/event-log hydration bridge artifacts.
Generated documentation books, manifests, search indexes, JSONL proof records, and docs evidence through @shapeshift-labs/frontier-documentation.
A dev-mode floating inspect/debug/rewind button with structural state, patch, CRDT, event-log, trace, and telemetry channels.
Schema-backed config validation with semantic diagnostics, suggested fixes, and frontier config explain.
Configurable source policy for max Frontier components per file, max lines and characters per file, runtime-module ownership, include/exclude roots, warn/error enforcement, and full opt-out.
Hybrid harness gates for tests, model-checking fuzzers, benchmarks, browser probes, telemetry, and agent evidence.
Generated smoke, fast-check property/model fuzz, replay minimization, benchmark, browser, corpus, and replay harness templates under .frontier-framework/harness.
Runtime and sync adapter catalogs for Hono/Nitro/server functions, Automerge, Yjs, Electric shape streams, Zero query sync, and Frontier-native transports.
Agent-first artifacts under .frontier-framework/agent: capability manifest, MCP/tool manifests, CI evidence gates, Frontier workflow manifest, Frontier linter report, SARIF, feature map, replay script, runbook, readiness checks, and issue/PR handoff templates.
frontier doctor for config/source/script/deploy/harness readiness diagnostics before agents or deploy jobs run.
Incremental frontend route caching under .frontier-framework/cache/frontend, with dependency-stat fast paths for repeated unchanged TSX builds.

Default scaffold:

apps/
  web/
    src/routes/index.tsx
    src/components/HomeView.tsx
    src/runtime/dom-events.ts
    src/runtime/forms.ts
    src/runtime/tools.ts
    src/runtime/offline.ts
    src/runtime/test-api.ts
    public/styles.css
  api/
    src/handler.ts
packages/
  contracts/
    src/index.ts
    src/migrations.ts
frontier.config.mjs
vite.config.ts
features/app-shell.json
AGENTS.md
turbo.json

The frontend can deploy as static files. The backend can deploy separately anywhere that can adapt a Fetch-compatible handler or one of the declared transport contracts: Node, edge workers, serverless functions, realtime hosts, CRDT sync servers, event streams, or a custom host.

If frontend.routes is omitted, frontier build, frontier inspect, frontier deploy-plan, frontier doctor, frontier agent, and frontier harness discover TSX routes from apps/web/src/routes. Route-group folders such as (marketing) stay out of URLs, private folders such as _internal, excluded files such as -draft.tsx, and parallel slots such as @modal are ignored by default. File segments such as [id], $id, {-$category}, [...slug], [[...slug]], and $.tsx become Frontier dynamic, optional, and splat route params. Conflicting discovered route shapes fail early, and evidence builds write dist/frontier/route-discovery.json for agents.

frontier init my-app
cd my-app
npm install
npm run build
npx frontier config validate --json
npx frontier config explain sourcePolicy
npx frontier status home --json
npx frontier status --route /home --json
npx frontier status filter:counter-default --json
npx frontier coverage --json
npx frontier coverage --strict
npx frontier loop --json
npx frontier loop --strict
npx frontier surfaces --kind filter --status planned --json
npx frontier migrations --json
npx frontier docs build --json
npm run doctor
npm run agent
npm run agent:check
npm run agent:replay
npm run harness
npm run fuzz
npm run bench
npm run browser
npm run bench:package
npm run deploy:plan

The default build emits dist/frontend, dist/backend, and dist/frontier so deployment and evidence stay separate. Targeted --target frontend and --target backend builds stay focused on their deploy artifacts; run frontier build or frontier build --target evidence when you need evidence, harness, migration, documentation, and agent bundles. Frontend builds fingerprint the route plus its local component imports, store dependency mtimes/sizes, and reuse unchanged HTML/diagnostics from .frontier-framework/cache/frontend without rebundling fresh TSX. Evidence builds generate .frontier-framework/documentation, .frontier-framework/route-scenarios, .frontier-framework/surfaces, .frontier-framework/migrations, .frontier-framework/harness, .frontier-framework/agent, dist/frontier/documentation.json, dist/frontier/route-scenarios.json, dist/frontier/surfaces.json, dist/frontier/surface-coverage.json, dist/frontier/migrations.json, dist/frontier/config-validation.json, dist/frontier/source-policy.json, and a seed corpus under test/fixtures/frontier-framework-corpus. In strict mode, missing Vite, migrations, harness, fuzzer, benchmark, browser, or feature-manifest setup fails instead of silently producing partial evidence.

frontier docs [inspect|build|lint|test|fuzz|bench|jsonl] runs the framework-configured documentation pass. frontier docs build --json writes .frontier-framework/documentation plus dist/frontier/documentation.json, while frontier docs jsonl streams the machine-readable documentation proof and search records.

frontier config validate --json validates frontier.config.mjs against the exported schema and semantic rules for routes, route scenarios, generic surface statuses, backend transports, deploy outputs, source policy, harness gates, and agent handoff settings. It writes dist/frontier/config-validation.json and returns actionable diagnostics with suggested fixes. frontier config explain [path] prints the expected type, defaults, examples, and fix guidance for a config path such as vite.hmr, sourcePolicy, surfaces, routeScenarios, frontend.routes, or backend.transports.

routeScenarios lets apps declare route, auth/session/state fixture, redirect, DOM-role, selector, scroll, and console expectations without Frontier owning the app-specific fixture data. Builds write .frontier-framework/route-scenarios/manifest.json plus a generated Playwright plan. surfaces is the generic status registry for pages, routes, filters, features, actions, resources, or app-owned surface kinds; apps define lifecycle statuses, aliases, and evidence links, while Frontier derives untracked route/feature records so agents do not treat a file or route as verified merely because it exists. surfaces.intents is the agent shorthand for declaring a route/page/filter/action surface once; Frontier expands each intent into a normal status record and, for route/page/view/component intents, a generated route scenario skeleton unless disabled. createSurfaceStatusReport(...), frontier status, and frontier surfaces query that registry by ref, id, kind, route, feature, owner, status, or tag, and the report includes a compact coverage snapshot with ok, missing probes, nextCommand, and planned probe records for every matched surface. createSurfaceCoverageReport(...) and frontier coverage join claimed statuses to render/state/evidence probes, write .frontier-framework/surfaces/coverage.json plus .frontier-framework/surfaces/dashboard.md, emit per-probe buckets and next-probe commands, attach a normalized frontier-test acceptance run/proof when the CLI verifies coverage, and can fail with --strict or surfaces.coverage.failOnMissing. createFrontierAgentLoopReport(...) and frontier loop join the status report and coverage report into .frontier-framework/agent/surface-loop.json plus a configurable focus dashboard that defaults to the next missing route, page, filter, or action evidence. The loop JSON also includes an ordered workQueue with stable work ids, surface refs, probe kinds, suggested commands, required flags, expected artifacts, and acceptance hints so agents can pick the next task without parsing dashboard prose.

frontier migrations --json writes dist/frontier/migrations.json, .frontier-framework/migrations/migrations.json, and .frontier-framework/migrations/frontier-runtime-migrations.mjs. The generated bridge exposes createFrontierStateMigration(...) for createStateEngine(..., { migration }) and createFrontierCachePersistenceMigration(...) for persistQueryCache(..., { migrateSnapshot }), while still allowing apps to call migrateRuntimeData(...) directly for CRDT snapshots, event-log snapshots, DOM state, and custom sources.

HMR is enabled by default for the Vite dev server path. Set vite.hmr: false in frontier.config.mjs to disable hot module reloading; vite.devServer.hmr remains supported as a lower-level alias, but vite.hmr takes precedence when both are set.

sourcePolicy is enabled by default with preset: 'adapter', enforcement: 'error', maxFrontierComponentsPerFile: 1, maxLinesPerFile: 320, and maxCharsPerFile: 24000. New scaffolds use preset: 'strict-app', strict TypeScript compiler defaults, and app-wide source scanning. Use preset: 'migration' or conformance.mode: 'migration' for warning-only staged ports. Runtime controller modules can be declared with defineRuntimeModule, bindDomEvents, bindFormActions, bindToolSurface, bindOfflineSnapshot, and bindTestApi; source-policy evidence records ownership such as form-actions, tool-surface, or offline-snapshot and rejects missing, unchecked, or duplicate controller ownership. Set a rule to false to disable just that rule, set enforcement: 'warn' for advisory diagnostics, or set enabled: false to turn the policy off for a project.

The devtools overlay installs globalThis.__FRONTIER_FRAMEWORK_DEVTOOLS__ and, by default, globalThis.__FRONTIER_DEVTOOLS__ when the app has not already provided one. Apps can call attachBridge() to connect a custom state engine, or call the default bridge directly with setState, recordPatch, recordCrdtUpdate, recordEventLogEntry, recordTrace, and recordTelemetry. Evidence builds write dist/frontier/devtools-bridge.json so agents know which channels and methods are available.

The generated fuzz harness uses fast-check when installed, reads corpus and replay files, runs a deterministic fallback model otherwise, checks route/transport/patch/event/CRDT/telemetry invariants, and writes minimized failures. The benchmark harness records route materialization, app-state replay, evidence indexing, and telemetry redaction rows. The browser harness uses Playwright when installed to assert DOM, state, route evidence, devtools bridge, patch, CRDT, event-log, trace, and telemetry probes in one machine-readable browser-harness.json run.

The agent bundle is meant to be machine-readable first. frontier agent --json writes agent-manifest.json, agent-actions.json, agent-checkpoints.json, feature-map.json, surface-loop.json, surface-loop.md, mcp-tools.json, tool-manifest.json, ci-evidence-gates.json, frontier-agent-lint.json, frontier-agent-lint.sarif, agent-workflow.json, agent-workflow-proof.json, frontier-agent-replay.mjs, agent-readiness.json, AGENT-RUNBOOK.md, HANDOFF.md, ISSUE-HANDOFF.md, and PR-HANDOFF.md. Agents can run frontier loop --strict --json before selecting work, frontier doctor --json before handoff, node .frontier-framework/agent/frontier-agent-check.mjs before handoff, and node .frontier-framework/agent/frontier-agent-replay.mjs --required-only when another agent or CI job needs to replay the same evidence gates.

Package-local framework overhead can be checked with npm run bench:package -- --cli-build --out dist/frontier/harness/framework-package-benchmark.json.

Related Packages

The published Frontier package family is generated from one shared package catalog so READMEs stay in sync across packages:

@shapeshift-labs/frontier: Core JSON diff/apply, compact patch tuples, JSON Pointer, equality, clone, validation, Unicode helpers, and tiny dependency-free runtime budget/scheduler primitives.
@shapeshift-labs/frontier-query: Shared query-key, selector path, condition, entity identity, and table-shape primitives.
@shapeshift-labs/frontier-codec: Patch serialization, binary frames, canonical JSON, and patch-history codecs.
@shapeshift-labs/frontier-engine: Stateful planned diff engine, adaptive profiles, schema plans, and engine-level history helpers.
@shapeshift-labs/frontier-state: Patch-routed app-state subscriptions, owned commits, maintained views, and path mapping.
@shapeshift-labs/frontier-dataflow: Serializable incremental dataflow and materialized-view graphs for Frontier apps, including selectors, dependency DAGs, filters, joins, aggregations, stale paths, recompute budgets, output patches, provenance records, and proof of why derived views changed.
@shapeshift-labs/frontier-state-cache: Normalized query-result cache with entity/query watchers, persistence, change logs, optimistic layers, scheduled persistence, and mutation bridge.
@shapeshift-labs/frontier-state-cache-idb: IndexedDB persistence adapter for Frontier state-cache snapshots and durable change logs.
@shapeshift-labs/frontier-state-cache-file: Structured file persistence adapter for Frontier state-cache snapshots and change logs.
@shapeshift-labs/frontier-state-cache-sql: SQL persistence adapter for Frontier state-cache snapshots and change logs.
@shapeshift-labs/frontier-schema: JSON Schema validation, Frontier profile generation, CloudEvent envelopes, and query/table schema helpers.
@shapeshift-labs/frontier-migrations: Boundary-first data migrations, import normalization, plugin/API version mapping, versioned envelopes, graph diagnostics, patch path rewrites, dry-run reports, and current-shape rehydration.
@shapeshift-labs/frontier-event-log: Bounded event logs, replay cursors, consumer acknowledgements, keyed compaction, checkpoints, and Frontier patch event records.
@shapeshift-labs/frontier-inspect: Cross-package inspection/evidence bundles, registry graph snapshots, feature/resource impact reports, timeline/event normalization, redaction, JSONL import/export, and AI-readable app feature maps.
@shapeshift-labs/frontier-scheduler: Deterministic work scheduling, lanes, cancellation, backpressure, frame policies, replay snapshots, and work graphs.
@shapeshift-labs/frontier-logging: Opt-in structured logging, browser telemetry, scheduled sinks, file sinks, exporters, benchmark traces, and Frontier patch/update summaries.
@shapeshift-labs/frontier-mutation: Explicit mutation and selector plans compiled to Frontier patches or CRDT operations.
@shapeshift-labs/frontier-effects: Serializable effect descriptors and resource graphs for Frontier apps, including fetch, storage, timers, navigation, workers, clipboard, broadcast, WebSocket, stream, policy metadata, runtime records, redaction, JSONL, proof helpers, and registry graph output.
@shapeshift-labs/frontier-auth: Frontier-native auth contracts for providers, sessions, profile completeness, route and resource gates, account-linking policy, token issue/verify plans, runtime grants, audit events, registry graphs, lint resources, and auth evidence without owning app secrets, crypto, storage, or provider SDKs.
@shapeshift-labs/frontier-policy: Serializable policy and capability decisions for Frontier apps, effects, views, sync, routes, traces, and AI tools.
@shapeshift-labs/frontier-flags: Patchable policy-aware feature flag state for Frontier apps, including targeting, deterministic rollouts, experiment variants, kill switches, exposure records, audit logs, and replay evidence.
@shapeshift-labs/frontier-tools: Serializable app action/tool manifests for AI-operable Frontier apps, including availability, validation, dry-run plans, patch previews, effect/tool constraints, execution records, rollback links, and registry graph output.
@shapeshift-labs/frontier-sandbox: Runtime-agnostic sandbox contracts for Frontier patch-producing actions, including manifests, declared reads/writes/capabilities, host-validated patch/effect/event/log results, dynamic source modules, source event replay, and structural runtime adapters.
@shapeshift-labs/frontier-sandbox-quickjs: QuickJS/WebAssembly runtime adapter for Frontier sandbox actions, including invocation/runtime isolation modes, deadline and memory limits, dynamic source execution, and patch/effect result normalization.
@shapeshift-labs/frontier-workflow: Serializable durable workflow/process manifests for Frontier apps, including steps, waits, approvals, timers, retries, expected patches, compensation, records, timelines, and registry graph output.
@shapeshift-labs/frontier-worker: Serializable worker and edge task descriptors for Frontier apps, including queues, idempotency keys, retry and timeout policy, declared reads/writes/effects, snapshots, patch outputs, produced assets, execution records, logs, trace links, proof hashes, dedupe indexes, and registry graph output.
@shapeshift-labs/frontier-queue: Serializable durable queue state, leases, retries, dedupe keys, patch-carrying jobs, dead-letter records, replay evidence, and queue inspection for Frontier apps.
@shapeshift-labs/frontier-swarm: Hierarchical swarm plans, lanes, compute profiles, ownership policy, semantic ownership regions, task queues, event streams, run records, merge bundles, merge indexes, queue overlays, merge admission, coordinator dashboards, changed-path checks, and proof artifacts for Frontier agent work.
@shapeshift-labs/frontier-swarm-codex: Node Codex CLI adapter for Frontier swarm plans, including prompt rendering, worktree and snapshot workspaces, Codex argument compatibility, browser resource allocation, JSONL capture, verification commands, pid-backed stop, collect/apply workflows, merge indexes, queue overlays, merge bundles, normalized job evidence, coordinator query artifacts, and result artifacts.
@shapeshift-labs/frontier-lang-kernel: Runtime-neutral semantic source graph, type/lattice/extern declarations, patch bundles, replay, hashing, evidence records, and merge-admission kernel for Frontier Lang.
@shapeshift-labs/frontier-lang-parser: Dependency-light Frontier Lang parser for modules, entities, state, actions, effects, types, externs, targets, and lattice declarations.
@shapeshift-labs/frontier-lang-checker: Checker and diagnostics for Frontier Lang semantic documents, including type symbols, effects, regions, lattice laws, CRDT metadata, and patch evidence.
@shapeshift-labs/frontier-lang-typescript: TypeScript projection adapter for Frontier Lang semantic documents, including type/entity/state/action/extern declarations and CRDT lattice descriptors.
@shapeshift-labs/frontier-lang-javascript: JavaScript projection adapter for Frontier Lang semantic documents, including ESM action stubs and schema/lattice descriptors.
@shapeshift-labs/frontier-lang-rust: Rust projection adapter for Frontier Lang semantic documents, including structs, aliases, and action stubs.
@shapeshift-labs/frontier-lang-python: Python projection adapter for Frontier Lang semantic documents, including dataclasses, typed patch records, and action stubs.
@shapeshift-labs/frontier-lang-c: C header projection adapter for Frontier Lang semantic documents, including structs and action prototypes.
@shapeshift-labs/frontier-lang-compiler: Compiler facade for Frontier Lang source documents, including parse, check, hash, diagnostics, universal AST envelopes, proof/paradigm semantic summaries, projection to TypeScript, JavaScript, Rust, Python, and C, and native source-import adapters for semantic merge evidence.
@shapeshift-labs/frontier-lang-swift: Swift source-language importer package for Frontier Lang semantic documents, including package-level metadata, SwiftSyntax adapter helpers, native import results, and semantic sidecar generation for SwiftSyntax/SwiftParser-shaped syntax trees.
@shapeshift-labs/frontier-lang-kotlin: Kotlin PSI source-language importer package for Frontier Lang semantic documents, including package-level metadata, Kotlin PSI adapter helpers, native import results, and semantic sidecar generation for Kotlin PSI/KtFile-shaped syntax trees.
@shapeshift-labs/frontier-lang-java: Java source-language importer package for Frontier Lang semantic documents, including package-level metadata, Java AST adapter helpers, native import results, and semantic sidecar generation for javac/JDT/JavaParser-shaped ASTs.
@shapeshift-labs/frontier-lang-go: Go source-language importer package for Frontier Lang semantic documents, including package-level metadata, Go AST adapter helpers, native import results, and semantic sidecar generation for go/ast File or Package trees.
@shapeshift-labs/frontier-lang-csharp: C# Roslyn source-language importer package for Frontier Lang semantic documents, including package-level metadata, Roslyn adapter helpers, native import results, and semantic sidecar generation for SyntaxTree/SyntaxNode-shaped ASTs.
@shapeshift-labs/frontier-lang-clang: Clang AST source-language importer package for Frontier Lang semantic documents, including package-level metadata, Clang AST JSON adapter helpers, native import results, and semantic sidecar generation for C/C++ translation units.
@shapeshift-labs/frontier-lang-cli: Command line interface for parsing, checking, hashing, emitting, native source import/projection, semantic slicing, and corpus roundtrip evidence for Frontier Lang projects.
@shapeshift-labs/frontier-lang: Umbrella package for Frontier Lang kernel, parser, checker, compiler facade, universal AST helpers, projection adapters, and source-language importer adapters.
@shapeshift-labs/frontier-kv: Serializable in-memory key/value state for Frontier apps, including TTL, versioned compare-and-set, batched patch mutations, scans, watchers, snapshots, JSONL event evidence, and replay verification.
@shapeshift-labs/frontier-kv-locks: Lease-style lock records on top of Frontier KV, including acquire, renew, release, fencing tokens, expiration, owner evidence, and replayable lock events.
@shapeshift-labs/frontier-kv-rate-limit: Patch-native rate limit buckets for Frontier KV, including fixed windows, sliding windows, token buckets, deterministic refill, consume evidence, and reset records.
@shapeshift-labs/frontier-kv-file: Node file persistence adapter for Frontier KV snapshots and append-only JSONL event logs, including atomic writes, compaction, replay loading, and adapter evidence.
@shapeshift-labs/frontier-kv-idb: IndexedDB persistence adapter for Frontier KV snapshots and event logs, with structural IDB interfaces, upgrade planning, compact event storage, and replay loading.
@shapeshift-labs/frontier-kv-redis: Redis-compatible command planning and structural client adapter for Frontier KV operations, including key mapping, TTL commands, optimistic CAS scripts, and replay evidence without bundling Redis drivers.
@shapeshift-labs/frontier-kv-server: Small Node HTTP server adapter for Frontier KV, including request planning, JSON endpoints for get/set/delete/scan/batch, optional rate-limit hooks, and replayable response evidence.
@shapeshift-labs/frontier-assets: Serializable asset and content provenance graphs for Frontier apps, including source files, generated variants, thumbnails, LOD chunks, shader/material dependencies, transforms, hashes, owners, runtime consumers, review plans, registry graph output, and impact queries.
@shapeshift-labs/frontier-blueprint: Serializable Blueprint/Prefab flyweight templates for Frontier apps, including parameterized instantiation, deterministic ID/path remapping, compact overrides, variants, effective-state materialization, scene/state patch emission, dependency metadata, and registry graph output.
@shapeshift-labs/frontier-triggers: Capability-gated event trigger registry, scoped event envelopes, listener/reaction rules, structured rejection, deterministic event-to-action scheduling, replay/provenance records, and registry graph output.
@shapeshift-labs/frontier-virtual: DOM-neutral virtualization, layout providers, range materialization, grids, spatial/frustum indexes, patch invalidation, camera anchors, and serializable layout state.
@shapeshift-labs/frontier-table: Renderer-neutral data grid and table primitives for Frontier apps, including stable row identity, sorting, filtering, selection, virtual ranges, patch-driven edits, cache/dataflow descriptors, and CRDT-compatible row and cell operation frames.
@shapeshift-labs/frontier-scene: Patch-native 2D/3D scene graph, transform propagation, bounds queries, virtual/culling adapters, spatial invalidation, and camera/frustum materialization.
@shapeshift-labs/frontier-pathfinding: Patch-native grid pathfinding, typed-array A*/Dijkstra search, flow fields, connected components, line-of-sight smoothing, dirty-cell invalidation, and scheduler-friendly path jobs.
@shapeshift-labs/frontier-lod: Patch-native level-of-detail and significance selection for rendering and computation workloads, compact typed hot paths, multi-observer selection, budget degradation, materialization frames, and scheduler work plans.
@shapeshift-labs/frontier-route: DOM-neutral app/game route resources, route and scene manifests, match/resolve/transition planning, dependency metadata, sessions, registry graph output, and impact queries.
@shapeshift-labs/frontier-trace: Serializable traces, spans, events, causal links, W3C trace context helpers, timeline/resource/path queries, critical-path analysis, registry graph output, JSONL/proof helpers, Chrome trace export, and redaction for app-wide feature observability.
@shapeshift-labs/frontier-manifest: Build/static feature manifests for owners, routes, actions, states, migrations, tests, source files, assets, resources, tasks, dependency metadata, registry graph output, feature maps, JSONL export, and impact queries.
@shapeshift-labs/frontier-view: Renderer-neutral view manifests, type defaults, validation frames, action bindings, visual channels, virtual/LOD hints, and data-to-representation mapping for Frontier apps.
@shapeshift-labs/frontier-icons: Renderer-neutral icon records, icon sets, lookup aliases, SVG frames, string rendering, and registry evidence for Frontier apps.
@shapeshift-labs/frontier-design: Renderer-neutral design-system tokens, semantic roles, recipes, target style frames, CSS variable output, and registry graph evidence for Frontier apps.
@shapeshift-labs/frontier-canvas: Renderer-neutral infinite canvas surfaces for Frontier apps, including camera and viewport math, pan/zoom plans, grid materialization, snapping, hit testing, selection handles, extensible tool dispatch, frame records, registry graph output, and impact/proof helpers.
@shapeshift-labs/frontier-canvas-tools: Renderer-neutral editor tools, state machines, transform handles, permissions, async records, and AI action bridges for Frontier canvas surfaces.
@shapeshift-labs/frontier-dnd: Renderer-neutral drag-and-drop sessions, sensor descriptors, collision ranking, drop planning, reorder patches, state partitioning, and registry evidence for Frontier apps.
@shapeshift-labs/frontier-dom: Patch-native DOM and host renderer bindings, manifest hydration, JSX runtime/compiler helpers, SSR, devtools, and logging bridges.
@shapeshift-labs/frontier-playwright: Playwright/headless automation probes for Frontier state, DOM, devtools, marks, and timeline queries.
@shapeshift-labs/frontier-test: Serializable test/spec evidence manifests for Frontier apps, including fixtures, commands, expected patches/effects/routes/policies, coverage declarations, run plans, run records, report adapters, replay proofs, fuzzers, benchmarks, registry graph output, and impact queries.
@shapeshift-labs/frontier-fixtures: Deterministic fixture and scenario generation for Frontier apps, including schema-valid sample state, related entity collections, actor personas, route states, replay-verified patch streams, event records, JSONL bundles, and evidence summaries.
@shapeshift-labs/frontier-component-preview: Frontier-native component preview books, generated preview manifests, stateful variants, Vite virtual modules, standalone browser preview shells, inspector bridges, and preview harness evidence for Frontier apps.
@shapeshift-labs/frontier-documentation: Frontier-native documentation manifests, generated documentation books, package/API/source discovery, Vite virtual modules, standalone browser docs shells, inspector bridges, search indexes, and documentation harness evidence for Frontier apps and packages.
@shapeshift-labs/frontier-ast-walk: Dependency-light source graph, import/export/declaration/call analysis, Frontier package-use discovery, and business-logic placement findings for Frontier tools, apps, docs, fuzzers, benchmarks, and agent evidence.
@shapeshift-labs/frontier-history: Serializable temporal explanation and causality records for Frontier apps, including field-change explanations, action/workflow/policy/effect/trace/test provenance, audit windows, undo planning, registry/provenance graph output, JSONL replay bundles, and proof hashes.
@shapeshift-labs/frontier-application: Serializable whole-application graph and impact queries for Frontier apps, including features, owners, packages, routes, views, actions, mutations, state paths, effects, workers, assets, tests, traces, policies, workflows, migrations, benchmarks, registry graph output, feature maps, JSONL bundles, and proof hashes.
@shapeshift-labs/frontier-linter: Serializable Frontier lint rules, diagnostics, fixes, reports, and fast rule execution for package catalogs, registry graphs, application maps, manifests, traces, policies, workflows, workers, assets, tests, benchmarks, and source snippets.
@shapeshift-labs/frontier-crdt: Native CRDT documents, update tooling, awareness, branches, conflict introspection, version frames, and undo.
@shapeshift-labs/frontier-crdt-sync: CRDT sync endpoints, repo/storage/provider contracts, scheduled sync work, document URLs, local networks, model checking, forensics, and text binding contracts.
@shapeshift-labs/frontier-crdt-websocket: WebSocket client/server transports for Frontier CRDT sync providers.
@shapeshift-labs/frontier-react: React external-store hooks and adapters for Frontier state, cache, and CRDT surfaces.
@shapeshift-labs/frontier-richtext: Rich text Delta normalization/application, marks, embeds, ranges, and cursor/selection transforms for local editor integrations.
@shapeshift-labs/frontier-realtime: Shared realtime command, tick, snapshot, prediction, reconciliation, interpolation, rollback, message, and delta primitives.
@shapeshift-labs/frontier-realtime-server: Authoritative realtime room, tick, command validation, rate-limit, session, and snapshot-history runtime.
@shapeshift-labs/frontier-realtime-websocket: WebSocket client, wire, and Node room-server transport for Frontier realtime.
@shapeshift-labs/frontier-game: Game-facing entity, component, player, room, ownership, spatial interest, rollback, physics, and replication helpers above realtime.
@shapeshift-labs/loom: Repo-level semantic collaboration CLI for .loom workspaces, including init, scan, status, graph snapshots, projection plans, Frontier Lang delegation, Frontier Swarm delegation, and optional Frontier Framework delegation.

Package source repositories:

Pkg
Stats

Discover Tips

General search

Package details

User packages

Sponsor

About

Twitter

GitHub

Twitter

GitHub

Site

Open Software & Tools

Framework

Server

Data Store

Caching

CSS / Styling

Typeface

Avatars

Data Viz

Date formatting

Infinite scrolling

Markdown rendering

Repository url parsing

User data

Compiling

Types

Odds & Ends

@shapeshift-labs/frontier-framework

v0.1.4

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

@shapeshift-labs/frontier-framework

Related Packages