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

text-number-parser

v0.1.1

Published

Parse localized Unicode number words into JavaScript number and bigint values.

Readme

text-number-parser

CI npm version

Parse localized Unicode number words into JavaScript number or bigint values.

Features

  • TypeScript source with generated declaration files.
  • Narrow public API with throwing and non-throwing parse functions.
  • Unicode-aware tokenization and normalization.
  • Parser modes for connector words and hyphenated input.
  • Extensible lexicons for custom scale words and localization.
  • Typed error objects for empty input, invalid tokens, and invalid number syntax.
  • Vitest coverage for the public API.
  • Tinybench suite for quick performance checks.

Installation

npm install text-number-parser

Usage

import {
  InvalidTokenError,
  createParser,
  parseTextNumber,
  tryParseTextNumber,
} from "text-number-parser";

parseTextNumber("one hundred and twenty-one");
// 121

parseTextNumber("nine quadrillion nine trillion");
// 9009000000000000n

parseTextNumber("one hundred and one", { allowAnd: false });
// throws InvalidSyntaxError

const result = tryParseTextNumber("twenty hundred million cat");

if (!result.ok) {
  console.error(result.error.code, result.error.message);
}

try {
  parseTextNumber("two cats");
} catch (error) {
  if (error instanceof InvalidTokenError) {
    console.error(error.token, error.index);
  }
}

const indianParser = createParser({
  extendLexicon: [
    { word: "dozen", type: "multiplier", value: 12 },
    { word: "lakh", type: "multiplier", value: 100_000 },
    { word: "crore", type: "multiplier", value: 10_000_000 },
  ],
});

indianParser.parse("three crore five lakh");
// 30500000

const spanishParser = createParser({
  lexicon: [{ word: "veintidós", type: "number", value: 22, cls: "teen" }],
  locale: "es",
  normalization: "NFC",
});

spanishParser.parse("VEINTIDO\u0301S");
// 22

Public API

parseTextNumber(input, modes?)

Parses an English number phrase and returns either a number or a bigint when the value exceeds Number.MAX_SAFE_INTEGER.

Supported modes:

type ParserModes = {
  allowAnd?: boolean;
  allowHyphen?: boolean;
};

tryParseTextNumber(input, modes?)

Returns a discriminated union:

type ParseResult =
  | { ok: true; value: number | bigint }
  | { ok: false; error: TextNumberError };

createParser(options)

Builds an isolated parser instance with its own lexicon, default modes, locale-aware lowercasing, and Unicode normalization strategy.

type CreateParserOptions = {
  lexicon?: Iterable<LexiconEntry>;
  extendLexicon?: Iterable<LexiconEntry>;
  locale?: string | string[];
  normalization?: "NFC" | "NFD" | "NFKC" | "NFKD" | false;
  modes?: ParserModes;
};

englishLexicon

Readonly default English lexicon used by the top-level parser.

Error classes

  • TextNumberError
  • EmptyInputError
  • InvalidTokenError
  • InvalidSyntaxError

Each error carries the original input. Token and syntax errors also expose the offending token and character index.

Supported language rules

  • Units: zero through nine
  • Teens: ten through nineteen
  • Tens: twenty through ninety
  • Multipliers: hundred, thousand, million, billion, trillion, quadrillion
  • Optional filler: and
  • Optional sign prefix: minus, negative
  • Hyphenated inputs are accepted by default and can be disabled with allowHyphen: false
  • Connector words can be disabled with allowAnd: false

Extensibility

  • Use extendLexicon to add new words such as dozen, lakh, and crore.
  • Use lexicon to replace the default dictionary entirely for localization.
  • Unicode words are normalized before lookup, so composed and decomposed forms can resolve to the same entry.

Development

npm install
npm run build
npm test
npm run bench