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

see

v0.0.0

Published

Grep inspired tool to find references inside JavaScript files.

Readme

see Build Status

Grep inspired tool to find references inside JavaScript files.

Installation

npm install -g see

Usage

see

Current status

In development, minimal functionality (just prints matching lines so far).

Features it will have

  • when logging a match to the console, include the enclosing scope to provide context (i.e. show the entire function that contained the match instead of just the line on which the match was found)
  • to ignore matches found inside comments and/or strings
  • limit matches to function names, variable names, etc., only

Features it may have

  • syntax highlight matches
  • interactive mode supplementing cli
  • .see per project file for local defaults
  • .see per user file for global defaults

CLI options

  • --maxlines max num of lines per match (i.e. if containing function body is larger than that, we only print part of it)
  • --comments include matches found inside comments
  • --strings includes matches inside strings
  • --nowarn don't print warning when file was unparsable by acorn
  • --nocolor don't syntax highlight matches
  • --function match calls to functions and function declarations
  • --funcdec match function declarations only