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

dom-inspect

v0.1.1

Published

Point at any DOM element in the browser and get the source file and line number

Readme

dom-inspect

Point at any element in the browser and instantly get its source file, line number, and CSS properties.

Available as a Vite plugin (npm) and a Chrome extension.

Vite Plugin

npm install -D dom-inspect
// vite.config.ts
import { sourcePicker } from 'dom-inspect'

export default defineConfig({
  plugins: [
    react(),
    sourcePicker(),
  ]
})

Injects data-source attributes on every JSX element at compile time. Zero production impact — everything is stripped in prod builds.

Chrome Extension

Works on any website. Click the extension icon to enable per-site.

  • With the Vite plugin: shows source file + line number + CSS properties
  • Without: shows tag, classes, and computed CSS properties

Load from chrome-extension/ as an unpacked extension.

How to Use

| Action | What it does | |---|---| | Tap Alt (Option on Mac) | Toggle inspect mode on/off | | Hold Alt + move mouse | Inspect mode while held | | Hover | Highlights element, shows source info | | Arrow Up / Down or Scroll wheel | Navigate the component hierarchy | | Click | Pin tooltip, show CSS details | | Click again | Copy source path to clipboard | | Escape | Unpin or exit inspect mode |

What the Tooltip Shows

  • Element tag, source file location, hierarchy position
  • CSS properties: layout, spacing, colors (with Tailwind class resolution)
  • Color swatches with hex values

Why

When working with AI coding assistants, the biggest friction is pointing at which element you mean. This tool maps DOM elements back to source locations — hover, copy, paste into your conversation.

React 19 removed _debugSource from fibers, breaking tools like click-to-react-component. This uses a Babel transform instead.

License

MIT