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 🙏

© 2024 – Pkg Stats / Ryan Hefner

findead

v1.2.3

Published

Dead react components finder

Downloads

460

Readme

:mag: findead

Dead react components finder

NPM Version NPM Downloads Run Tests

:rocket: Dead Components is the Motivation

Many times in large or even small projects, we forgot some components in code that we'll never use and we never take time to search one by one and remove.

:camera: Demonstration

Demonstration When findead finish, you'll can see:

  • Components name
  • Path of each one component
  • Size of each one file
  • How many dead components
  • How many browsed files
  • How much time spent to execution

:computer: Tech

Just bash :)

:inbox_tray: Install

  • Npm
npm i -g findead
  • Yarn
yarn add findead

:hammer: Usage

findead <folder_to_get_components>

Pass folder to get all of your components in js, jsx, ts and tsx files.

obs: By default, all node_modules folder is ignored.

:zap: Examples

Just one argument

  • If you pass just one argument, it will be used for get components and search usages
findead ~/path/to/search

Raw result

  • Pass -r flag for raw output. Better for atribute output into a file.
findead -r ~/path/to/search

Multiple and specific folders

findead -m ~/path/to/search/{folder1,folder2,...,folderN}