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

@r4pm/components

v0.2.0

Published

Reusable viewers (DFG, Petri net, dotted chart, OCEL, alignments) and inputs for process mining

Readme

@r4pm/components

React components for process mining.

Components include Petri net, object-centric Petri net, directly-follows graph (DFG and OC-DFG), dotted chart, alignments (list and net), case-duration and events-per-time charts, log and OCEL summaries, plus inputs (frequency picker, choosers).

Install

pnpm add @r4pm/components
# peer dependencies:
pnpm add react react-dom

Use

import "@r4pm/components/styles.css";
import { Theme, PetriNetViewer } from "@r4pm/components";

<Theme>
  <PetriNetViewer data={net} />
</Theme>;

Import @r4pm/components/styles.css once (it bundles Tailwind + the Radix theme). A viewer's root sizes inline so it fills its container immediately; inner layout uses that stylesheet. Shared coloring, formatting, and interactivity are configured once via ViewerConfigProvider (see the Storybook "Concepts > Viewer Configuration" page).

Subpaths

Heavier viewers live behind subpaths so the core entry stays light (importing @r4pm/components never pulls Plotly or the Petri-net editor):

| Import | Contents | | --- | --- | | @r4pm/components | viewers (DFG, Petri net viewer, OCEL summaries, alignments, ...), inputs, feedback states, and the presentation contract: ViewerProps, ViewerConfig, ViewerConfigProvider, useViewerConfig, colorForKey, colorForSeed | | @r4pm/components/ui | the Radix Themes seam (Theme, Button, Card, ...). Import UI primitives from here, never @radix-ui/themes directly | | @r4pm/components/petri | the React Flow + ELK Petri-net editor (layout, export controls) | | @r4pm/components/charts | Plotly-backed viewers: DottedChart, CaseDurationChart, EventsPerTimeChart, ObjectAttributeChangesChart, ActivityChart, ThemedPlot | | @r4pm/components/styles.css | precompiled stylesheet (Tailwind + Radix theme) |

Docs

Storybook is the component gallery and API reference (props tables are generated from the TypeScript types). Most components ship a *.stories.tsx with sample data.

pnpm --filter @r4pm/components dev        # local gallery (storybook dev)
pnpm --filter @r4pm/components showcase   # static build -> storybook-static/