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

@repo2ds/react

v0.1.0

Published

React framework adapter for Repo2DS: component discovery, prop extraction, style extraction and Storybook generation.

Readme

@repo2ds/react

React adapter for Repo2DS. Finds components, reads their props, and records the styles they declare inline or in imported stylesheets.

Most people want the CLI instead:

npx repo2ds scan ./my-project

Usage

import { DiagnosticCollector, AnalysisPipeline } from '@repo2ds/core';
import { ReactAdapter } from '@repo2ds/react';
import { TailwindStyleAdapter } from '@repo2ds/tailwind';

const rootDir = '/path/to/repo';
const diagnostics = new DiagnosticCollector();

const result = await new AnalysisPipeline({
  rootDir,
  diagnostics,
  adapters: [
    new ReactAdapter({
      rootDir,
      diagnostics,
      // Optional: interpret className utilities as styles.
      classStyleAdapter: new TailwindStyleAdapter(),
    }),
  ],
}).run();

What it recognises

  • Function components, arrow components, React.FC annotations and class components
  • Props from an interface, a type alias, an inline object type, or destructured parameters, with default values when they are statically visible
  • style={{ ... }} objects, including both branches of a conditional and nested objects
  • className strings, when a ClassStyleAdapter is supplied
  • Imported .css, .scss, .sass and .less files, resolving var(--token) references to the values declared in the same stylesheet

Anything that cannot be resolved without running the code is recorded as a dynamic value and left out of token inference rather than guessed.

ReactStoryGenerator writes Storybook CSF3 stories from a discovered component.

License

MIT