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

@react-trace/plugin-open-editor

v0.0.4

Published

react-trace plugin: open inspected component source in your code editor

Readme

@react-trace/plugin-open-editor

Open the currently selected component source in a local editor from the Trace action panel.

This plugin adds:

  • an Open in Editor action for the selected source
  • a settings control for choosing the default editor inside the widget

Installation

Install the plugin alongside its peer dependencies:

pnpm add --dev @react-trace/core @react-trace/ui-components @react-trace/plugin-open-editor

If you are already using @react-trace/kit, this plugin is included there by default.

Usage

import { Trace } from '@react-trace/core'
import { OpenEditorPlugin } from '@react-trace/plugin-open-editor'

import App from './App'

export function AppWithTrace() {
  return (
    <>
      <App />
      <Trace
        root={import.meta.env.VITE_ROOT}
        plugins={[OpenEditorPlugin({ editor: 'vscode' })]}
      />
    </>
  )
}

root should be the absolute project root passed to Trace so the plugin can resolve relative file paths for comments.

editor option

OpenEditorPlugin accepts a single option:

interface OpenEditorPluginOptions {
  editor?: EditorPreset
}
  • Default: vscode
  • If the user changes the editor in the widget settings, that's what's used instead.

The package also exports the EditorPreset type.

Supported editor presets

These are the currently implemented presets:

  • vscode
  • cursor
  • windsurf
  • webstorm
  • intellij

Behavior

When a source location is selected, the plugin resolves the file path relative to the Trace root and opens the generated editor URL with window.open(...).