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

@lovstudio/dsh-frontend-inspector

v0.1.1

Published

Lovstudio dev click-to-source for DeepSeek Harness web: runtime-only, reads React _debugSource on Shift+Option click and opens the editor. No build-time markers; works in vite dev (jsxDEV __source).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

markshawnmarkshawn

Keywords

deepseek-harnessdshdsh-pluginfrontend-inspectorlovinspclick-to-source

Readme

dsh-frontend-inspector

Lovstudio's dev-only click-to-source for the DeepSeek Harness web surface. Hold Shift + Option and click a rendered element to open the editor at that element's source location.

This is a Lovstudio plugin, not a DeepSeek-AI package, distributed under the @lovstudio scope.

What it does

The plugin is completely runtime — there are no build-time source transforms and no build-time data-insp-path markers.

  • Host half registers two webServer routes:
    • GET /lovinsp-inject.js — serves the runtime client script.
    • POST /lovinsp-open — receives { file, line, col } and opens the editor (open <scheme>://file/<file>:<line>:<col>).
  • Client (the served script): on Shift + Option click, walks the target element's React fiber (__reactFiber$) to the nearest custom component and reads its _debugSource (file:line:column), then POSTs it to /lovinsp-open.

Because it reads React's _debugSource, it works where the app is built with the JSX __source kept in development mode (a real vite/dev-server React app). Production builds strip __source, so the plugin is a dev-facing debug tool.

The plugin reaches DSH capabilities through the injected Cordis ctx only (webServer, and the settings service for the enabled switch). Its only package dependency is the schemastery schema library.

Install

Plugins distribute as a bundle (dsh.bundle.patch → cordis.patch.yml). Install into the web profile (the one dsh web boots):

# from git (append #<sha> to pin a commit)
dsh plugin --profile web add github:lovstudio/dsh-frontend-inspector

# or straight from npm
dsh plugin --profile web add @lovstudio/dsh-frontend-inspector

enabled defaults to true; a frontend-inspector.enabled settings namespace can override it. The webServer service is provided by the harness launcher / @deepseek-ai/dsh-base.

Use

  1. Start a dev web UI (one whose JSX keeps __source), or a dsh web served with vite dev-mode source info.
  2. Hold Shift + Option and click any element.
  3. The editor opens at the component's source.

Notes

  • Dev-only: requires React _debugSource present in the running bundle.
  • IDE open uses the OS open/xdg-open/start command with the configured URL scheme (default vscode). Override via the plugin scheme config.

License

MIT