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 🙏

© 2025 – Pkg Stats / Ryan Hefner

finse

v1.5.8

Published

A command line tool template

Readme

finse

Find which files reference the target file

Features

  • Friendly output
  • Supports alias via tsconfig.json
  • Supports esm and cjs
  • Detect the project root directory
  • Unlimited file types

Install

$ npm i -g finse
$ finse -h # help

Usage

Suppose we have a project, its directory structure is like this:

finse
  └─ test
      └─ demo
          ├─ bar
              ├─ corge
                  └─ nacho.vue
              └─ oop.ts
          ├─ foo
              └─ sharp.js # sdf
          └─ thud.tsx

And you want to find out which files reference oop.ts,just run:

$ finse test/demo/bar/oop.ts

Maybe you will see the output similar to this:

The yellow background represents the file you want to match, the cyan background is the file that "uses" it

API

--root [rootname]

  • Specify the project root directory

--expand

  • Expand collapsed file tree

--link

  • Display the absolute path of the file. That way other files can be accessed directly through the terminal

--ignore

  • Ignore file does not exist errors

Motivation

  • It's hard to find which other files use the target file

  • Search in IDEA is not enough, it's difficult to give exact search keywords

How is works ?

  • First, it will detect the project root directory if no directory is specified
  • By default, the directory where package.json is located is selected as the root directory
  • Next, all reasonable files in the directory will be scanned
  • Then match the contents of the file to see if there is an import statement
  • finse will recognize the following imports
// static import
import xx from 'xxx'

if (Math.random() > 0.5) {
  // dynamic import
  import('xx.ts')
}

// require import
require('./xx/xx')

finse works with regular expressions, But don't worry about "accidental recognition":

// Yes, legal import
import xx from 'xxx'

// No,Imports in comments are not recognized
// comment: import xx from 'xxx'

And supports identifying paths with alias:

<script setup>
import xx from '@/xx'
// or:
import xxx from '~/xx'
</script>

But have to make sure there is such a configuration in [t|j]sconfig.json:

{
  "compilerOptions": {
    "paths": {
      "~/*": ["test/demo/bar/*"],
      "@/*": ["src/*"]
    }
  }
}

finse

it's mean find use

Acknowledgement

Thanks for the proposal for jsconfig.json by Artsmp