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 🙏

© 2024 – Pkg Stats / Ryan Hefner

sane-regexp

v0.1.7

Published

A set of functions to build and compose complex regular expressions

Downloads

10

Readme

compose-regexp.js

A set of functions to build and compose complex regular expressions in JavaScript.

Works nicely with verbal expressions, even though the target user is likely different.

The goal of this library is to enable advanced RegExp users to write maintainable lexers and parsers. A reasonable understanding of the parsing model of regexps is a prerequisite.

Usage

$ npm install --save compose-regexp
import {
    sequence, either, capture,
    ref, greedy
} from "compose-regexp"; // can be required too

// the example that made me write this, in order to ~parse JS.
// It matches braces in source code, but skips comments and strings.
let matcher = flags('gm',
    either(
        sequence(
            capture(/['"`]/),
            greedy('*', // a greedy zero-or-more repetition
                either(
                    sequence('\\', ref(1)),
                    '\\\\',
                    sequence(avoid(ref(1)), /[\s\S]/)
                )
            ),
            ref(1)
        ),
        sequence(
            '/*',
            greedy('*',
                avoid('*/'),
                /[\s\S]/
            ),
            '*/'
        ),
        sequence('//', /[^\n]*\n/),
        capture(either(/[{}]/, '}}'))
    )
);

// matcher:

/(?:(['"`])(?:(?:\\\1|\\\\|(?!\1)[\s\S]))*\1|\/\*(?:(?!\*\/)[\s\S])*\*\/|\/\/[^\n]*\n|((?:[{}]|\}\})))/gm

// The most astute among you may have noticed that regexes in the subject string
// would still trip that parser. Not perfect, but still useful.

API

General (important) notes:

The regexp parameters of these functions can be either RegExps or strings. Special characters in strings are escaped, so that '.*' is equivalent to /\.\*/. Therefore:

> sequence('.', '*').source
'\\.\\*'

The flags of intermediate regexps are ignored, and always reset to false unless set by flags().

flags(opts, regexps...)

> flags('gm', /a/)
/a/gm

either(regexps...)

> either(/a/, /b/, /c/)
/(?:a|b|c)/

sequence(regexps...)

> sequence(/a/, /b/, /c/)
/abc/

group(regexps...)

> group(/a/, /b/, /c/)
/(?:abc)/

lookAhead(regexps...)

> lookAhead(/a/, /b/, /c/)
/(?=abc)/

avoid(regexps...)

Negative look ahead

> avoid(/a/, /b/, /c/)
/(?!abc)/

greedy(suffix, regexprs...)

Valid suffixes: (?, *, +, {n}, {n,} and {m, n})

> greedy("*", either(/a/, /b/, /c/))
/(?:a|b|c)*/
> maybe = greedy.bind(null, '?'); maybe(either('a', 'b'))
/(?:a|b)?/

frugal(suffix, regexprs...)

Like greedy() but for non-greedy operators (??, *?, +?, {n}?, {n,}? and {m, n}?).

> frugal("{1,3}", either(/a/, /b/, /c/))
/(?:a|b|c){1,3}?/

capture (regexprs...)

> capture(/a/, /b/, /c/)
/(abc)/

ref(n)

> ref(1)
/\1/

Caveat emptor, references are absolute. Therefore, refs may be broken if you compose two regexps that use captures.


stringMatcher = sequence(
    capture(/['"`]/),
    greedy('*', // a greedy zero-or-more repetition
        either(
            sequence('\\', ref(1)),
            '\\\\',
            sequence(avoid(ref(1)), /[\s\S]/)
        )
    ),
    ref(1)
)

whooops = sequence(
    capture('foo'),
    stringMatcher
)

In whoops, the ref(1) in stringMatcher actually refers to foo, not the opening quote.

Fixing this would require an approach far more complex than what I'm doing now (concat the regexps source).

Notes

This tool is very simple under the hood and its output is not optimised for either size or speed. For example, you may find that some non-capturing groups are superfluous. Getting rid of these would require parsing the regexps under the hood to simplify them, and it is beyond the scope of this project at this time.

License MIT

The MIT License (MIT)

Copyright (c) 2016 Pierre-Yves Gérardy

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.