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

@rahul_ur/devlink

v1.0.9

Published

Click any element in your browser → jump to source code → edit → UI updates live. One command setup for Vite, Next.js and CRA.

Readme

devlink

Click any element in your browser → jump to its source code → edit it → UI updates live.

Works with Vite, Next.js, and CRA. Fully local — no cloud, no API keys.


Install

npm install @rahul_ur/devlink
npm install -D @rahul_ur/devlink-babel-plugin @rahul_ur/devlink-vite-plugin

Setup (one command)

npx devlink setup

This automatically:

  • Detects your framework (Vite / Next.js / CRA)
  • Patches your vite.config.ts or .babelrc
  • Creates devlink.config.ts with your project paths
  • Adds devlink:bridge script to package.json

Add to your app entry

// src/main.tsx (Vite) or pages/_app.tsx (Next.js)
import { DevlinkBridge } from '@rahul_ur/devlink-bridge'
import { DevlinkStudio } from '@rahul_ur/devlink-studio'
import { devlinkConfig } from '../devlink.config'

const bridge = new DevlinkBridge()

function Root() {
  return (
    <DevlinkStudio bridge={bridge} {...devlinkConfig}>
      <App />
    </DevlinkStudio>
  )
}

Start the bridge server

Open a separate terminal and keep it running:

npm run devlink:bridge

Use it

Start your app normally (npm run dev) then:

| Action | How | |--------|-----| | Toggle inspect mode | Alt+D | | Click element → open source | Click any element | | Box select multiple | ⬚ Box button then drag | | Area capture | Hold + and drag | | Save file | Ctrl+S | | Exit inspect mode | Esc or right-click |


Vite config (manual)

If auto-setup didn't patch your config:

// vite.config.ts
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import { devlinkBabelConfig } from '@rahul_ur/devlink-vite-plugin'

export default defineConfig({
  plugins: [
    react({
      babel: {
        plugins: [
          devlinkBabelConfig({ root: process.cwd() }),
        ].filter(Boolean),
      },
    }),
  ],
})

Next.js config (manual)

// .babelrc
{
  "presets": ["next/babel"],
  "env": {
    "development": {
      "plugins": [
        ["@rahul_ur/devlink-babel-plugin", { "root": ".", "envs": ["development"] }]
      ]
    }
  }
}

DevlinkStudio props

| Prop | Type | Default | Description | |------|------|---------|-------------| | bridge | DevlinkBridge | required | Bridge instance | | projectRoot | string | required | Absolute path to your project root | | rootPath | string | required | Path shown in file tree (usually projectRoot/src) | | defaultDocked | boolean | false | Start editor docked to the right | | dockedWidth | number | 460 | Width of docked panel in px | | enabled | boolean | NODE_ENV=development | Disable entirely in production |


Packages

This package installs all of these automatically:

| Package | Purpose | |---------|---------| | @rahul_ur/devlink-bridge | WebSocket tunnel between browser and local filesystem | | @rahul_ur/devlink-studio | Floating Monaco editor + inspector + terminal + AI bar | | @rahul_ur/devlink-babel-plugin | Stamps data-source on every JSX element at build time | | @rahul_ur/devlink-vite-plugin | Wires babel plugin into Vite + React automatically |


How it works

Your browser app
  → clicks element
  → reads data-source="src/Button.tsx:9:4" (stamped by babel plugin)
  → sends to bridge over local WebSocket
  → bridge reads file from disk
  → editor opens file, highlights lines
  → you edit + Ctrl+S
  → bridge writes to disk
  → HMR reloads your app
  → UI updates

Everything stays on your machine. No cloud. No uploads.


License

MIT