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

@spilne/perfect-topology

v0.2.0

Published

Stream topology engine on the Perfect runtime — windows, joins, stage planning, distributed runs.

Readme

@spilne/perfect-topology

Stateful stream processing on top of @spilne/perfect-core. Declare a processing DAG — keyed state, time windows, stream joins, deduplication, checkpointing — and run it over any source or sink that implements the @spilne/perfect-core/connect contracts (Streamable, Sinkable, Acknowledgeable, …). A KafkaTopic from @spilne/perfect-kafka plugs in directly; so does an in-memory test double.

Install

bun add @spilne/perfect-topology

Not yet published to npm — install from the workspace for now.

Quickstart

import { ConsumerGroup, StreamTopology, TopologyRunner } from "@spilne/perfect-topology";

// clicks / counts: configured KafkaTopic, RedisStream, PgmqQueue, or any
// application endpoint implementing the connect contracts.
const topology = StreamTopology.source(clicks)
  .keyBy((e) => e.userId)
  .tumbling(60_000)
  .aggregate({
    init: () => ({ count: 0 }),
    add: (state) => ({ count: state.count + 1 }),
    emit: (key, window, state) => ({ key, window, count: state.count }),
  })
  .to(counts);

const handle = await TopologyRunner.run(topology, {
  group: ConsumerGroup("analytics"),
});

console.log(handle.metrics().itemsProcessed);
const exits = await handle.awaitExit();
await handle.shutdown();

Durable identities use distinct constructors (TopologyId, StageId, TopologyInstanceId, SourceRecordId, and StateCheckpointId) so values cannot be accidentally swapped across state and connector APIs. Connector offsets remain plain strings because their representation is backend-specific.

Stateless steps chain like a stream; keyed steps unlock windows and state:

StreamTopology.source(readings)
  .filter((r) => r.temp != null)
  .mapAsync(5, enrich) // concurrency-bounded async map
  .keyBy((r) => r.sensorId)
  .process({
    // per-key state machine
    init: () => ({ avg: 0 }),
    process: (state, r) => {
      const avg = state.avg * 0.7 + r.temp * 0.3;
      return {
        state: { avg },
        emit: { sensorId: r.sensorId, movingAvg: avg },
      };
    },
  })
  .to(sink);

Features

  • Builder — StreamTopology.source(...) with map / filter / mapAsync, keyBy → KeyedTopology, .to(sink) or .build()
  • Windows — tumbling, sliding, session, with aggregate and the count() / sum() shorthands; WindowManager underneath
  • Joins — windowed key joins between two keyed topologies (JoinBuffer)
  • Dedup — .dedupe(keyFn) per key
  • Execution — TopologyRunner.run(topology, { group }) → TopologyHandle with shutdown(), awaitExit(), isRunning(), and metrics() (throughput, buffer fill, backpressure stats)
  • Distribution — DistributedRunner + planStages split the DAG at explicit shuffle() boundaries into stages connected by a ShuffleTransport (Kafka-backed one in @spilne/perfect-kafka)
  • Partition state — state is namespaced by topology, stage, operator, and partition; fenced lease epochs prevent stale instances from committing. Redis and PostgreSQL provide durable atomic state/progress/dedupe commits
  • Rebalances — assignment restores state before delivery; revocation drains in-flight records, checkpoints, and releases the partition lease
  • Delivery — at-least-once publishes before committing state/progress and acknowledging the source. exactly-once is accepted only when source, sink, and state advertise the same transaction domain. PGMQ plus PgPartitionedStateBackend is the first fully atomic implementation
  • Supervision — sink, acknowledgement, checkpoint, and branch failures are observable through awaitExit() and interrupt sibling branches
  • Analysis — analyzeTopology returns TopologyWarnings for suspect DAGs before you run them

Links