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

@lde/text-normalization

v0.1.1

Published

Zero-dependency text folding (diacritic stripping and transliteration) for search index and query normalization

Readme

@lde/text-normalization

Zero-dependency text folding for search index and query normalization.

fold() produces a diacritic- and case-insensitive form of a string, applied identically at index time and query time so that a search index never diverges from the queries run against it (divergence = silent search misses).

import { fold } from '@lde/text-normalization';

fold('Møhlmann'); // 'mohlmann'
fold('Coöperatieve'); // 'cooperatieve'
fold('Straße'); // 'strasse'

It combines Unicode NFKD decomposition + combining-mark stripping (which folds é, ö, å, ç, …) with an explicit transliteration map for letters that do not decompose under NFKD (ø, æ, œ, ß, ð, þ, ł, đ, …).

When it’s needed

A search engine on its default locale often folds case and diacritics for you – Typesense v30 (verified) even folds the non-decomposing ø/æ/ß – so on the default locale fold() is redundant for search. It becomes necessary when:

  • Sorting – engines sort strings by raw code-point order with no collation, so a fold()-ed companion field is the only way to sort case- and diacritic-insensitively.
  • Stemming – enabling a language’s stemmer requires a non-default locale, which switches the tokenizer (Typesense → ICU) to one that preserves diacritics; the default folding is lost, and fold() restores diacritic-insensitive matching.

fold() is idempotent (fold(fold(x)) === fold(x)). Punctuation and word boundaries are preserved; tokenization is left to the search engine.

Because folded values are stored in the search index, the same fold() must be used at index time and query time, and any change to it requires a full rebuild.