npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@shapeshift-labs/frontier-manifest

v0.1.0

Published

Serializable static feature manifests and build impact maps for Frontier apps.

Readme

@shapeshift-labs/frontier-manifest

Build-time and static feature manifests for Frontier apps. frontier-manifest records owners, packages, features, routes, actions, state paths, migrations, tests, source files, assets, resources, and build tasks as serializable data that can be queried by AI harnesses, Playwright, inspect bundles, route/effect/trace tooling, migrations, and release gates without importing app runtime code.

It is intentionally runtime-neutral. Compilers, bundlers, route packages, DOM packages, Playwright adapters, and telemetry systems should pass structural manifest entries into this package rather than making this package import those higher layers.

API Shape

import {
  createManifest,
  createManifestFeatureMap,
  createManifestProof,
  createManifestRegistryGraph,
  encodeManifestJsonl,
  manifestImpact,
  parseCodeowners,
  queryManifest
} from '@shapeshift-labs/frontier-manifest';

const manifest = createManifest({
  codeowners: `
/src/todos/** @app/todos
/tests/todos/** @qa/todos
/public/** @app/assets
`,
  entries: [
    {
      id: 'feature.todos',
      kind: 'feature',
      feature: 'todos',
      package: '@app/todos',
      source: { file: 'src/todos/index.ts', symbol: 'TodosFeature' },
      files: ['src/todos/model.ts'],
      routes: ['/todos'],
      actions: ['todos.load', 'todos.toggle'],
      states: ['entities.todos'],
      resources: ['route:/todos'],
      tests: ['test.todos.load']
    },
    {
      id: 'action.todos.load',
      kind: 'action',
      feature: 'todos',
      package: '@app/todos',
      source: { file: 'src/todos/load.ts', line: 12, symbol: 'loadTodos' },
      files: ['src/todos/load.ts'],
      routes: ['/todos'],
      actions: ['todos.load'],
      states: ['entities.todos'],
      resources: ['fetch:/api/todos'],
      writes: ['entities.todos'],
      dependsOn: ['feature.todos'],
      tests: ['test.todos.load']
    }
  ],
  tasks: [
    {
      id: 'task.todos.build',
      command: 'vite build',
      feature: 'todos',
      package: '@app/todos',
      inputs: ['src/todos/**', '!src/todos/**/__generated__/**'],
      outputs: ['dist/todos/**'],
      dependsOn: ['action.todos.load']
    }
  ]
});

const byFile = queryManifest(manifest, { files: ['src/todos/load.ts'] });
const impact = manifestImpact(manifest, { changedFiles: ['src/todos/load.ts'] });
const featureMap = createManifestFeatureMap(manifest);
const registryGraph = createManifestRegistryGraph(manifest);
const jsonl = encodeManifestJsonl(manifest);
const proof = createManifestProof(manifest);
const ownerRules = parseCodeowners('/src/** @team/app');

void byFile;
void impact;
void featureMap;
void registryGraph;
void jsonl;
void proof;
void ownerRules;

Design Notes

  • Entries are plain JSON-like records for features, routes, scenes, actions, states, migrations, tests, sources, assets, packages, effects, triggers, components, and custom app surfaces.
  • Build tasks record commands, input globs, output globs, environment dependencies, owners, feature/package ids, and task dependency edges.
  • CODEOWNERS parsing uses last-match ownership per file and unions owners across multi-file entries or tasks.
  • Glob matching supports *, **, ?, leading slash normalization, and ! exclusion patterns for task inputs.
  • Query and impact APIs use lazy manifest indexes for exact feature, package, owner, file, asset, route, action, state, migration, test, resource, and tag lookups.
  • File queries also match task input globs, so changing src/todos/load.ts can surface the build/test tasks that would be affected.
  • Impact tracing starts only from explicit query fields, changed files, changed assets, changed resources, and ids; an empty impact input returns an empty result rather than the whole manifest.
  • Impact tracing expands selected entries through dependents, owner rules, changed files, changed assets, changed resources, and optional Frontier registry traversal.
  • Registry graph output turns manifest entries, tasks, and owner rules into Frontier registry entries, records, and edges for inspect, trace, Playwright, replay, or AI evidence bundles.
  • Feature maps group every feature's entries, tasks, owners, files, assets, routes, actions, states, migrations, tests, resources, packages, and tags into one AI-readable shape.
  • JSONL export/import keeps manifests streamable for build artifacts and replay logs, while createManifestProof provides a stable replay fingerprint.

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-policy: Serializable policy and capability decisions for Frontier apps, effects, views, sync, routes, traces, and AI tools.
  • @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-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-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-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-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-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-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.

Package source repositories:

Install

npm install @shapeshift-labs/frontier-manifest

Benchmarks

These are Frontier-only package measurements, not competitor comparisons.

Run package-local measurements:

npm run bench

The benchmark covers manifest creation, file/feature/owner queries, file/resource impact tracing, feature map creation, registry graph generation, JSONL encode/decode, proof generation, and manifest merge.

Latest local package benchmark on Node v26.1.0, darwin arm64, 1k entries and 20 rounds:

| Fixture | Median | p95 | | --- | ---: | ---: | | create-manifest-1000 | 39.95 ms | 42.56 ms | | query-file-1000 | 95.07 us | 113.81 us | | query-feature-1000 | 36.79 us | 48.77 us | | query-owner-1000 | 47.13 us | 56.34 us | | impact-file-1000 | 672.78 us | 1.14 ms | | impact-resource-1000 | 11.97 us | 17.34 us | | feature-map-1000 | 3.20 ms | 3.69 ms | | registry-graph-1000 | 16.11 ms | 21.26 ms | | jsonl-encode-1000 | 7.70 ms | 8.08 ms | | jsonl-decode-1000 | 7.55 ms | 9.32 ms | | proof-1000 | 8.33 ms | 9.45 ms | | merge-two-1000 | 8.45 ms | 10.27 ms |

Boundary

frontier-manifest depends only on @shapeshift-labs/frontier. It does not import route, DOM, Playwright, inspect, trace, migrations, logging, scheduler, state, CRDT, framework, or bundler packages.