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

@graphrefly/pure-ts

v0.48.0

Published

Pure TypeScript implementation of GraphReFly. Universal fallback sibling for the @graphrefly/graphrefly facade — works without Rust deps. Permanent first-class peer alongside @graphrefly/native and @graphrefly/wasm.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

clfhhcclfhhc

Keywords

reactivegraphautomationworkflowllmai-agentsharness-engineeringagent-harnesscausal-traceorchestrationstate-managementsignalsstreamingobservablecausal-tracinghuman-in-the-loopnatural-languagedurable-workflowframework-agnosticreactvuesveltenestjszero-dependency

Readme

@graphrefly/pure-ts

Frozen pure-TypeScript implementation of GraphReFly. Parity oracle for the Rust port — not for new feature work.

This package preserves the pure-TS implementation of GraphReFly that was the sole impl through v0.44.0. It exists to drive parity tests against @graphrefly/native (the napi-rs binding compiled from ~/src/graphrefly-rs/) through 1.0, and to serve as a transparent fallback for platforms where the native binding cannot run.

Lifecycle

  • Status: frozen at the 0.44.x line.
  • Allowed changes: parity-fix backports (Rust port surfaces a divergence; fix lands on both impls in lockstep) and spec-amendment lockstep updates (~/src/graphrefly/GRAPHREFLY-SPEC.md evolves; both impls move together). No new features. No refactors that don't have a parity-driven reason.
  • Sunset: removed from the workspace when 1.0 ships parity-stable across N consecutive zero-divergence releases on the parity job. After sunset the package is npm-deprecated (with a pointer to @graphrefly/graphrefly) but remains installable for users on banned-native-binary platforms who haven't migrated to WASM.

Why this exists (Phase 13.9, locked 2026-05-05)

See archive/docs/SESSION-rust-port-architecture.md Part 12 (Q1–Q7) and docs/implementation-plan.md Phase 13.9 in the repository root for the architectural narrative and the operational sequencing. Short version:

  1. The 2780-test suite is the highest-fidelity behavior oracle for the Rust port. Deleting it before 1.0 throws away the most valuable regression-detection asset on the project.
  2. The Rust port is mid-migration (M1 closed, M2–M6 ahead). Until each milestone closes, the public package needs a fallback for surfaces the binding doesn't cover yet.

What consumers should use

You probably want @graphrefly/graphrefly, which transparently delegates to the right impl per platform. Use @graphrefly/pure-ts directly only if you need the zero-native-dep build pinned (e.g. CI for a sandboxed platform, deterministic supply-chain audit).

Public API

Identical to @graphrefly/[email protected]. See the project README and the website/ docs for usage. The exports map mirrors the @graphrefly/graphrefly exports map exactly.

Source layout

src/ — full surface as of v0.44.0: core/ + graph/ + extra/ + patterns/ + compat/. See the project root CLAUDE.md for the layered structure. Tests live colocated and under src/__tests__/; benches under src/__bench__/.

Build

pnpm --filter @graphrefly/pure-ts build
pnpm --filter @graphrefly/pure-ts test
pnpm --filter @graphrefly/pure-ts bench

The tsup.config.ts post-build guardrail (assertBrowserSafeBundles) enforces that universal entry points do not transitively import node:* builtins. See docs/docs-guidance.md § "Browser / Node / Universal split" in the repo root.