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

@feel-dev/vite-plugin

v0.2.0

Published

Alt + right-click any UI element to see the full stack behind it: component → frontend code → API → backend handler → SQL → tables.

Readme

@feel-dev/vite-plugin

Alt + right-click any element in your React app and see the full stack behind it:

component → the JSX line that rendered it → the functions that fetched its data
  → API route → backend handler → SQL queries → tables (+ structure, related tables, recent changes)

Every step opens the actual code. Built for understanding apps you didn't write line by line.

Dev only — nothing is added to production builds.

Install

npm install -D @feel-dev/vite-plugin @feel-dev/node

Set up

1. Frontend — vite.config.js:

import feel from '@feel-dev/vite-plugin';

export default defineConfig({
  plugins: [
    feel({ database: process.env.DATABASE_URL }), // before react()
    react(),
  ],
});

database is optional. With it, the panel can show table structure, relations and recent changes (Postgres only — MySQL queries and tables show per request without it).

2. Backend — first line of your server entry file (Express + pg, mysql2, Prisma or Drizzle):

import '@feel-dev/node/register';        // ES modules
// or
require('@feel-dev/node/register');      // CommonJS

It must come before anything that loads your routes or database code.

3. Proxy your API through Vite (or allow the X-Feel-Route response header cross-origin — @feel-dev/node already exposes it):

server: { proxy: { '/api': 'http://localhost:3001' } }

Use

  • Hold Alt and move the mouse — elements outline with their component name.
  • Alt + right-click — opens the panel: component chain, the code, and the data flow.
  • List / Graph toggle — the same flow as a list or a left-to-right graph.
  • Calls the component could make but hasn't yet (found in the code) show as possible calls, dashed in the graph.
  • Esc closes it.

What it understands

| | | |---|---| | Data fetching | fetch, axios (+ axios.create instances), custom hooks, wrapper functions, React Query, SWR | | Imports | relative, Vite resolve.alias, tsconfig/jsconfig paths + baseUrl, package.json "imports" | | Backend | Express 4/5 (app.get, router.get, app.route(), app.use('/prefix', router)) | | Database access | pg, mysql2 (MySQL / MariaDB), Prisma (7, or 6 with @prisma/adapter-pg), Drizzle (node-postgres, mysql2); SQL from other ORMs on pg | | Possible queries | pool.query('SQL'), pool.execute('SQL'), prisma.<model>.<op>() (tables from schema.prisma, incl. @@map), Drizzle select().from() / joins / insert / update / delete / db.query.<table> (tables from pgTable('name'), mysqlTable, sqliteTable) | | Database | Postgres: tables per query (read/write), columns, keys, foreign keys both ways, change history (opt-in triggers). MySQL / MariaDB: tables per query (read/write) |

Requirements

  • React 19 in development mode (for exact component usage lines; falls back to a DOM-based chain otherwise)
  • Vite 5+
  • Node 20.19+

Good to know

  • Change tracking is off until you click "Turn on change tracking" in the panel. It adds a feel_audit table and a trigger per table to the database you point it at — use it on a dev database.
  • The agent only reads source files inside your project — plus your Prisma schema, for model → table names — and never .env or other non-code files.