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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fixdog

v0.0.5

Published

Option+Click any React component to see its source location

Downloads

444

Readme

fixdog-sdk

Option+Click any React component to instantly see its source location.

fixdog
GIF demo placeholder goes here

Quick start (3 steps)

  1. npm install fixdog-sdk
  2. In your app entry, import and init:
    import { init } from "fixdog-sdk";
    init();
  3. Option/Alt + click a component in the browser to log its source.

Installation

  • Next.js / Vite / CRA: npm install fixdog-sdk (or yarn add, pnpm add)
  • Works in React 16.8+ through React 19. No runtime deps.

Usage

import { init, Inspector } from "fixdog-sdk";

// simple
init();

// with options
init({
  borderColor: "#ff6b6b",
  onClick: (info) => console.log("clicked", info),
});

// manual control
const inspector = new Inspector({ enabled: true });
inspector.activate();
inspector.deactivate();
inspector.destroy();

React provider (optional)

import { InspectorProvider } from "fixdog-sdk/react";

export function App() {
  return (
    <InspectorProvider options={{}}>
      <YourApp />
    </InspectorProvider>
  );
}

Options

| option | type | default | description | | ----------------- | ----------------------------- | -------------- | ---------------------------------------- | | onClick | (info) => void | undefined | Called on click with source info | | onHover | (info \| null) => void | undefined | Called when hover target changes | | shortcut | string | ctrl+shift+x | Toggle persistent inspect mode | | useOptionClick | boolean | true | Enable Option/Alt + click activation | | enabled | boolean | !production | Auto-disabled in prod unless forced true | | zIndex | number | 999999 | Overlay/tooltip stacking | | borderColor | string | #61dafb | Highlight + tooltip border color | | tooltipPosition | 'auto' \| 'top' \| 'bottom' | auto | Tooltip placement preference |

API

  • init(options?)Inspector singleton (auto-activates)
  • new Inspector(options?) → manual instance
    • .activate() enable listeners and overlay
    • .deactivate() remove listeners and hide overlay
    • .destroy() cleanup overlay
  • InspectorProvider React wrapper (optional)

SourceInfo

interface SourceInfo {
  componentName: string;
  fileName: string;
  lineNumber: number;
  columnNumber: number;
  fiber?: any; // raw React fiber
  element?: Element; // DOM element
}

How it works

  • Grabs the nearest React fiber on Option/Alt click (or persistent mode).
  • Walks up the fiber tree to _debugSource for fileName:line:column.
  • Shows an overlay + tooltip; logs formatted message and passes full info to callbacks.

Troubleshooting

  • Source not available: Ensure dev/build has _debugSource (development or React Refresh). Production builds often strip it.
  • Next.js / RSC: Server Components don’t have client-side fibers; ensure the inspected component is a client component.
  • Plain HTML element: No React fiber → nothing to log.
  • Iframes / shadow DOM: Inspector stays within the current document; shadow hosts are walked, but cross-iframe is skipped.

Testing locally

  1. npm install
  2. npm link
  3. Create a test app (e.g., npm create vite@latest test-app -- --template react-ts)
  4. In that app: npm link fixdog-sdk
  5. Import and run init() in main.tsx, then Option/Alt+click in the browser.

Build

  • npm run build (Rollup → ESM + CJS + types)
  • npm run dev (watch)

Contributing

PRs welcome. Please keep the bundle lean and TypeScript strict.

License

MIT © fixdog