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

compromise-strict

v0.0.2

Published

Formal parser for the compromise match syntax

Readme

The compromise match syntax is a custom language for matching and querying tags and metadata in a document.

This plugin is an experimental re-write of this syntax using a formal parser (chevrotrain) and a strict spec.

This may be useful for some purposes, where recursive queries, or error-reporting is required.

This library implements a subset of the match-syntax, and has different edge-cases.

It does add 135kb to filesize, so is not meant as a replacement of the default match method.

This library can be used to generate rail-road diagrams of match queries, or to test them for syntax errors. Pre-compiling matches may result in small, but noticable performance improvements over the native .match().

import nlp from "compromise";
import plugin from "compromise-strict";

nlp.extend(plugin);

let doc = nlp("hello world")
  .strictMatch("(?P<greeting>hi|hello|good morning) #Noun")
  .groups("greeting");
console.log(doc.text());

commonjs:

const nlp = require("compromise");
nlp.extend(require("compromise-strict"));

let doc = nlp("Good morning world")
  .strictMatch("(?P<greeting>hi|hello|good morning) #Noun")
  .groups("greeting");
console.log(doc.text());

Pre-Compling

strict has the ability to pre-compile a match statement into a parsed format, which may improve performace of the match query. This plugin automatically adds this as a helper-method on the main nlp constructor.

// ... rest from usage above
const m = nlp.preCompile("(?P<greeting>hi|hello|good morning) #Noun");
let doc = nlp("hello world").strictMatch(m).groups("greeting");
console.log(doc.text());

Supported RegexP grammar

  • StartOf: ^ - start of string
  • Value: can be repeated
    • Any: . - match any word
    • Tag: #Noun - part of speech / tags
    • Word: hello - just the word
      • EscapedWord: \#Noun matches the word #Noun
    • Group: (...) - match groups, will also capture which saves group content, values of ... will be matched.
      • Or: (value0|value1|value2 value3) - matches either value statements in group.
      • Named: (?P<name>...) - saves group which can later be accessed by name
      • NonCapturing: (?:...) - don't save group's matched content
      • Positive Lookahead: (?=...) - does not consume, asserts that group matches ahead
      • Negative Lookahead: (?!...) - does not consume, opposite of positive lookahead
    • Modifiers: goes at the end of value, ex: Hi+
      • Plus: + - matches one or more occurances of value
      • Star: * - matches zero or more occurances of value
      • Question: ? - matches zer or one occurance of value
      • Non Greedy Matches: +?, *?, ?? match as little as possible while still maintining a match.
      • Note: repeatedly matched groups will overwrite and save only the last value.
  • EndOf: $ - end of string

Railroad diagrams

image

Chevrotrain has the neat ability to generate diagrams to explain the match lookup. You can see an example of this working in ./lib/gen_diagram.js

GPL-3