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

@mosetta/ide-plugin-symbols

v0.0.14

Published

Go to definition, and the list of usages with a preview — one key for both.

Readme

Symbols

@mosetta/ide-plugin-symbols · Go to definition, and the list of usages with a preview — one key for both.

What it does

Put the caret on a name and press Cmd+B (Ctrl+B), or Cmd-click it:

  • on a usage, you jump to its definition;
  • on the definition, a list of usages opens next to the name, with the code around each one in a preview. Arrows move, Enter goes there.

Import lines are hidden from the list by default — they are usages in name only — and a switch in the list brings them back. The answers come from the language server, so they are as good as the server's understanding of the project.

The plugin also parses the project's TypeScript symbols in the background on the daemon's side, which is what makes functions, classes and interfaces findable in search everywhere.

Keys

| Command | macOS | Windows and Linux | |---|---|---| | symbol.goto — definition, or usages | Cmd+B, Cmd+click | Ctrl+B, Ctrl+click |

Screenshots and demos

The usages of a class, with a preview of each

From a usage to the definition, and from the definition to every usage

Watch the video · Try it in the browser

Using it from another plugin

The symbols plugin has no registry keys of its own; it is a consumer. It answers the editor's onSymbolAsk, asks the language servers plugin for definition and references, and adds a search.source for symbols.

To ask the same questions from your plugin, go to the language servers plugin directly:

import LspPlugin from '@mosetta/ide-plugin-lsp';

const lsp = this.ide.getPlugin(LspPlugin);
const sites = await lsp.references('src/flock.ts', 6, 14);
for (const site of sites) console.log(site.path, site.line, site.preview);

Its state is on the instance for anything that wants to draw the same list:

import SymbolsPlugin from '@mosetta/ide-plugin-symbols';

const { symbols } = this.ide.getPlugin(SymbolsPlugin);
symbols.hideImports.value = false; // show import lines in the usages list