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

@a5i/eregex

v0.1.5

Published

Node.js bindings for eregex, an advanced regular expression engine inspired by mrab-regex

Downloads

186

Readme

@a5i/eregex (Node.js bindings)

Native Node.js bindings for eregex — an advanced regular expression engine for Rust inspired by mrab-regex (the Python regex module).

This package exposes eregex's full API to JavaScript / TypeScript via napi-rs. All matching logic runs in compiled Rust; the JavaScript layer is a thin adapter.

Features

  • Named groups, duplicate group names, repeated captures
  • Greedy / lazy / possessive quantifiers, atomic groups (?>...)
  • Variable-length lookbehind / lookahead
  • Inline scoped flags (?i), (?i-m:...)
  • Backreferences \1, \g<name>, (?P=name)
  • Partial / end-anchored matching (findPartial)
  • find, matchAtStart (Python re.match), fullMatch (re.fullmatch)
  • replace, replaceAll with $1 / ${name} / $$ templates
  • split, escape, and more

Build

The native addon is built locally from the Rust core:

cd crates/eregex-node
npm install
npm run build        # release build → index.js + eregex.<platform>.node
# or: npm run build:debug

index.js, index.d.ts and the .node binary are generated by the build; they are not checked in.

Quick start

const { Regex, IGNORECASE, parseFlags } = require('@a5i/eregex');

const re = new Regex(String.raw`(\w+)\s+(\w+)`);
const m = re.find('hello world');
console.log(m.matched);      // 'hello world'
console.log(m.group(1));     // 'hello'
console.log(m.group(2));     // 'world'

// Flags: pass a bitset of the exported constants, or parse a string.
new Regex('hello', IGNORECASE).isMatch('HELLO');         // true
new Regex('hello', parseFlags('i')).isMatch('HELLO');    // true

// Repeated captures (signature mrab-regex feature).
new Regex(String.raw`(\w)+`).find('abc').captures(1);    // ['a', 'b', 'c']

// Replace with named groups.
new Regex(String.raw`(?P<a>\d)(?P<b>\d)`).replaceAll('12 34', '${b}${a}'); // '21 43'

Regex

class Regex {
  constructor(pattern: string, flags?: number)
  get pattern(): string
  get flags(): number         // resolved flags (defaults UNICODE + VERSION1 are added)
  get captureCount(): number  // capturing groups (group 0 excluded)
  groupNames(): string[]
  groupIndex(name: string): number | null

  isMatch(haystack: string): boolean
  find(haystack: string): Match | null
  findAt(haystack: string, start: number): Match | null
  matchAtStart(haystack: string): Match | null   // like re.match
  fullMatch(haystack: string): Match | null       // like re.fullmatch
  findAll(haystack: string): Match[]
  findPartial(haystack: string): PartialMatch | null

  replace(haystack: string, repl: string): string
  replaceAll(haystack: string, repl: string): string
  split(haystack: string): string[]
  dump(): string                                  // parsed AST (debug aid)
}

flags is a bitwise OR of the exported constants: IGNORECASE, MULTILINE, DOTALL, UNICODE, ASCII, VERBOSE, FULLCASE, WORD, LOCALE, VERSION0, VERSION1. parseFlags("ims") parses a flag string for RegExp-familiar ergonomics.

Match

class Match {
  get matched(): string       // whole match (group 0)
  get input(): string         // original haystack
  get start(): number         // byte offset
  get end(): number
  get span(): { start: number; end: number }
  get captureCount(): number
  get groups(): (string | null)[]             // current text, group 0 first
  get namedGroups(): Record<string, string>
  get allCaptures(): (string | null)[][]      // repeated-capture history
  get capturesDict(): Record<string, (string | null)[]>

  group(index: number): string | null
  namedGroup(name: string): string | null
  captures(index: number): (string | null)[]
  capturesByName(name: string): (string | null)[]
  spanOf(index: number): { start: number; end: number } | null
}

All offsets are byte offsets (UTF-8), matching Python's re and the Rust core. null is returned for groups that did not participate.

Partial matching

findPartial is an end-anchored search: it asks whether the haystack, taken up to its end, could be the start of a full match. Use it when validating input as the user types, parsing an incomplete stream, or asking "could more input turn this into a match?"

It returns one of three outcomes:

| result | meaning | | ------------------------ | ------------------------------------------------------------- | | PartialMatch (partial) | a valid prefix so far — more input could complete it | | PartialMatch (full) | the input already fully matches (and consumes it to its end) | | null | a hard mismatch: no possible continuation could match |

Each capturing group in a partial match is itself in one of three states, reported by groupState(i): 'matched' (fully matched), 'partial' (entered but not yet completed), or 'none' (never participated — group(i) is null).

class PartialMatch {
  get status(): 'full' | 'partial'
  get isFull(): boolean
  get isPartial(): boolean
  get matched(): string
  get start(): number          // byte offset where the match starts
  get end(): number            // byte offset of the input end (always haystack.length)
  get captureCount(): number

  group(index: number): string | null
  namedGroup(name: string): string | null
  groupState(index: number): 'matched' | 'partial' | 'none'
}

Incremental typing graduates partialfullnull:

const re = new Regex(String.raw`abc`);
re.findPartial('');     // null      (nothing started yet)
re.findPartial('a');    // partial   .status === 'partial'
re.findPartial('ab');   // partial
re.findPartial('abc');  // full      .isFull === true
re.findPartial('abcd'); // null      ('d' rules out any continuation)

Group states as a match fills in. With token=([a-z]+)([0-9]+)([A-Z]+):

const re = new Regex(String.raw`token=([a-z]+)([0-9]+)([A-Z]+)`);
const p = re.findPartial('x token=abc');

p.isPartial;            // true
p.matched;              // 'token=abc'
p.start;                // 2    (byte offset of the match)
p.end;                  // 11   (end of input — always, since end-anchored)
p.captureCount;         // 3

p.group(1);             // 'abc'   p.groupState(1); // 'matched'
p.group(2);             // ''      p.groupState(2); // 'partial'  (entered, empty so far)
p.group(3);             // null    p.groupState(3); // 'none'     (never entered)

re.findPartial('token=abc123XYZ');  // group 3 -> 'matched', status 'full'
re.findPartial('x token=abc!');     // null   ('!' rules out any continuation)

Named groups work the same way:

const re = new Regex(String.raw`token=(?P<word>[a-z]+)(?P<num>[0-9]+)`);
const p = re.findPartial('token=ab');
p.namedGroup('word');   // 'ab'   (matched)
p.namedGroup('num');    // ''     (partial — empty so far)

Module-level helpers

escape(s: string): string
escapeSpecialOnly(s: string): string
escapeLiteralSpaces(s: string): string
isMatch(pattern: string, haystack: string): boolean  // compiles pattern once
parseFlags(flagStr: string): number

Testing

npm test    # runs test/smoke.js

Layout

This is one half of eregex's binding story. The same Rust core (eregex) also ships Python bindings via pyo3 + maturin. See the project root for the core crate and its feature matrix.

License

Apache-2.0, matching the upstream mrab-regex project.