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

close-enough

v1.1.0

Published

String comparison allowing for arbitrary differences

Downloads

24

Readme

NPM version Build Status Dependency Status

close-enough

String comparison allowing for arbitrary differences.

Install

$ npm install --save close-enough

Usage

const closeEnough = require('close-enough');

// Create a comparator instance
const ce = closeEnough();

// Basic string comparison
ce.compare('Hello World', 'hello world'); // true - case insensitive
ce.compare('abc def', 'def abc'); // true - word order doesn't matter
ce.compare('café', 'cafe'); // true - diacritical marks are ignored

// Different strings
ce.compare('abc def', 'abc xyz'); // false

// Separators and spacing are normalized
ce.compare('hello-world', 'hello world'); // true
ce.compare('hello/world', 'hello_world'); // true
ce.compare('hello   world', 'hello world'); // true

// Extra words are ignored (shorter string must be subset of longer)
ce.compare('abc def', 'abc zzz def'); // true
ce.compare('abc def ghi', 'abc def'); // true

// Get similarity score (0 = identical, higher = more different)
ce.score('hello world', 'hello world'); // 0
ce.score('hello world', 'hello earth'); // 0.5

Advanced Usage

Filtering Generic Words

Remove common words that should be ignored during comparison:

const ce = closeEnough().generics(['hotel', 'inn', 'suites']);

ce.compare('Holiday Inn Hotel', 'Holiday Suites'); // true

Using Synonyms

Define words that should be treated as equivalent:

const ce = closeEnough().synonyms({
  'street': 'st',
  'avenue': 'ave',
  'road': 'rd'
});

ce.compare('Main Street', 'Main St'); // true
ce.compare('Park Avenue', 'Park Ave'); // true

Chaining Configuration

You can chain multiple configuration methods:

const ce = closeEnough()
  .generics(['hotel', 'inn', 'resort'])
  .synonyms({
    'street': 'st',
    'avenue': 'ave'
  });

ce.compare('Grand Hotel on Main Street', 'Grand Inn on Main St'); // true

API

  • compare(a, b) - Returns true if strings are considered close enough, false otherwise
  • score(a, b) - Returns a numeric score indicating difference (0 = identical)
  • generics(array) - Configure generic words to ignore during comparison
  • synonyms(object) - Configure word synonyms for comparison

License

MIT © Damian Krzeminski