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

dupes

v0.0.6

Published

A command line tool for finding duplicate files

Downloads

25

Readme

dupes - WIP

Build Status NPM Version License

A command line tool for finding duplicate files

dupes helps you find duplicate files.

This is a work in progress.


Installation

$ npm install -g dupes

Usage

dupes [directory] will search that directory for duplicate files and write a dupes.json results file.

Ommiting the [directory] will run the commands on the current directory.

dupes-read [filePath] will open that directory's .json file and output its results.

Ommiting the [filePath] will open 'dupes.json' in the current directory.

See dupes -h and dupes-read -h for more options.


How does it work?

dupes works by running a list of differentiation methods - each one seperates the current pools of files into smaller pools. Pools of size 1 are then ommited. The current differentiation methods are:

  • File size - Very fast, filters out a lot of files, but obviously still leaves different files together.
  • MD5 of the whole file - Slower but definite.

Each method has a different trade-off of speed and accuracy. By starting with the cheapest methods, we make sure that more expensive ones will be executed on a smaller amount of files. By finishing with a whole-file-checksum, we guarantee that files deemed identical are indeed so.


TODOs

  • Allow rewriting of dupes.json files if they are signed
  • Implement an option to run only on files from old result
  • Implement better ways to read results (largest files, largest groups)
  • Add option to limit files checked to certain sizes.
  • Add option to include or exclude files/folders by name/regex, and set default excludes.
  • Turn this list into github issues.
  • Find duplicate folders.
  • Check if separateFilesByHeadMD5 (commented out) will work better with bigger file size limitations.
  • Try searching for a hash function faster than md5.
  • Write dupes-gui, a web gui to write and read dupes results in the browser with express.
  • Change array style to comma-before.
  • ...