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

@react-state-map/cli

v0.1.6

Published

CLI tool to visualize React state flow through static analysis

Readme

React State Map

Instantly visualize how state flows through your React application.

React State Map analyzes your codebase and generates interactive diagrams showing exactly how state, props, and context flow between components. No runtime dependencies, no code changes required - just pure static analysis.

React State Map Demo

Installation

# Run directly with npx (no install required)
npx @react-state-map/cli ./src

# Or install globally
npm install -g @react-state-map/cli

Usage

# Analyze current directory, output to state-map.html
react-state-map

# Analyze specific directory
react-state-map ./src

# Custom output file
react-state-map ./src --output my-state-map.html

# Output as JSON (for programmatic use)
react-state-map ./src --format json --output state.json

# Watch mode - auto-regenerate on file changes
react-state-map ./src --watch

# Don't auto-open in browser
react-state-map ./src --no-open

# Set prop drilling threshold
react-state-map ./src --threshold 4

# Include/exclude patterns
react-state-map ./src --include "**/*.tsx" --exclude "**/test/**"

Options

| Option | Short | Default | Description | |--------|-------|---------|-------------| | --output <file> | -o | state-map.html | Output file path | | --format <format> | -f | html | Output format: html or json | | --watch | -w | false | Watch for file changes | | --threshold <n> | -t | 3 | Prop drilling threshold (hops) | | --no-open | | false | Don't open output in browser | | --include <patterns> | -i | **/*.tsx,**/*.jsx | Glob patterns to include | | --exclude <patterns> | -e | node_modules,... | Glob patterns to exclude |

What It Detects

State Types

| State Type | Detection | |------------|-----------| | useState | Variable name, initial value | | useReducer | Reducer name, initial state | | useContext | Context name, provider/consumer | | Redux | useSelector, useDispatch | | Zustand | useStore, useXxxStore patterns | | Custom Hooks | Any useXxx hook calls |

Visualization Features

  • State Flow: See which components own state and how it propagates
  • Directory Clustering: Components grouped by folder structure
  • Context Boundaries: Visualize React Context providers with clustered consumers
  • Collapsible Subtrees: Click to collapse/expand component subtrees
  • Prop Drilling Detection: Automatically detect props passed through too many layers

Output

HTML (default)

Generates a standalone, interactive HTML file with:

  • Blue nodes = Components with local state
  • Green nodes = Stateless components
  • Green arrows = Props flow
  • Purple dashed arrows = Context flow
  • Gray dashed boundaries = Directory clusters
  • Purple boundaries = Context provider scope
  • ▼/▶ indicators = Collapsible nodes
  • Red highlights = Prop drilling paths

Pan, zoom, collapse/expand nodes, click components for details, and switch between views.

State Flow View

JSON

{
  "components": [...],
  "edges": [...],
  "contexts": [...],
  "stats": {
    "totalComponents": 42,
    "statefulComponents": 12,
    "propDrillingPaths": 3
  }
}

Use Cases

| Challenge | Solution | |-----------|----------| | "Where does this prop come from?" | Visual trace from source to destination | | "Which components use this context?" | Context boundary visualization | | "Is this prop drilling?" | Automatic detection with hop count | | "What state does this component have?" | Click any node to see details | | CI/CD documentation | Generate HTML reports automatically | | Code reviews | Share state flow visualizations |

VS Code Extension

For real-time visualization while coding, use the VS Code extension.

Requirements

  • Node.js 18.0.0 or higher
  • React project with .tsx or .jsx files

License

MIT

Feedback & Issues

Open an issue on GitHub