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

@zoerai/tag-selector

v0.0.4

Published

Click any JSX element to see its source code location

Downloads

10

Readme

@zoerai/tag-selector

Click any JSX element to see its source code location - Zero config required! 🎯

A developer tool that allows clicking any JSX element to see its source code location. Works with Next.js Turbopack.

Features

  • Zero Config - Works out of the box with sensible defaults
  • 🎯 Click to Inspect - Click any element to see its source file and line number
  • 🔍 Visual Overlay - Hover and selection indicators
  • 🚀 Next.js Turbopack - Native integration
  • 🛡️ Production Safe - Only runs in development mode
  • 🎨 Non-invasive - Automatically skips Fragments, Suspense, and ErrorBoundary

Installation

npm install @zoerai/tag-selector

Quick Start

1. Configure Next.js (One Line!)

// next.config.ts
import type { NextConfig } from "next";
import { turbopackInspectorPlugin } from "@zoerai/tag-selector/turbopack";

const nextConfig: NextConfig = {
  turbopack: {
    rules: turbopackInspectorPlugin(), // 👈 That's it!
  },
};

export default nextConfig;

2. Add Inspector Component

// app/layout.tsx
import { Inspector } from "@zoerai/tag-selector/components";

export default function RootLayout({ children }) {
  return (
    <html>
      <body>
        {children}
        <Inspector /> {/* 👈 Add the inspector */}
      </body>
    </html>
  );
}

3. Start Developing

Press Ctrl + Shift + C (Windows/Linux) or Cmd + Shift + C (Mac) to toggle inspector mode, then click any element!

Advanced Configuration

All options are optional with smart defaults:

turbopackInspectorPlugin({
  // File patterns to process (default: "**/*.{jsx,tsx}")
  include: "**/*.{jsx,tsx}",

  // Additional exclusions (default: [])
  // Note: node_modules is already excluded automatically
  exclude: ["**/excluded-folder/**"],

  // Attribute name for storing path data (default: "data-insp-path")
  attributeName: "data-insp-path",

  // Tags to skip injection (default: ["Fragment", "Suspense", "ErrorBoundary"])
  escapeTags: ["Fragment", "Suspense", "ErrorBoundary", "MyWrapper"],

  // Run before other loaders (default: true)
  enforcePre: true,
})

How It Works

  1. Build Time: Babel plugin injects data-insp-path attributes into JSX elements
  2. Runtime: Inspector component listens for click events
  3. Inspection: Reads the attribute and displays source location
  4. Production: Automatically disabled when NODE_ENV !== 'development'

Development

# Install dependencies
npm install

# Build the library
npm run build

# Watch mode
npm run dev

# Run tests
npm run test

# Type checking
npm run typecheck