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 🙏

© 2025 – Pkg Stats / Ryan Hefner

heregex

v1.0.1

Published

ES6 tagged template to make regular expressions more easily readable.

Downloads

12

Readme

heregex

ES6 tagged template to make regular expressions more easily readable.

Add comments using the # character prefixed with a space. All whitespace gets removed (so use \s for actual whitespace matching). Any flags go in ${'gim'} at the end of the string.

Examples

heregex = require('heregex')

let regex_github_repo = heregex`
  ^                    # start of string
  (?:https?:\/\/)?     # optional http/https
  (?:www\.)?           # optional "www."
  github\.com          # website address
  \/
  ([a-z0-9_-]+)        # username ($1)
  \/
  ([a-z0-9_-]+)        # repo ($2)
  (?:\.git)?           # optional .git
  ${'i'}
`;

Which creates this end result:

/^(?:https?:\/\/)?(?:www\.)?github\.com\/([a-z0-9_-]+)\/([a-z0-9_-]+)(?:\.git)?/i

The end result of that example is still readable, but if you're doing even slightly more complex regular expressions, multiple lines with comments becomes a lot easier to read:

heregex = require('heregex')

let regex_number = heregex`
    ^0b[01]+                   # binary
  | ^0o[0-7]+                  # octal
  | ^0x[0-9a-f]+               # hex
  | ^\d*\.?\d+ (?:e[+-]?\d+)?  # decimal
  ${'i'}
`;

which compiles down to the harder to read version:

/^0b[01]+|^0o[0-7]+|^0x[0-9a-f]+|^\d*\.?\d+(?:e[+-]?\d+)?/i

Installation

npm install --save heregex

or

yarn add heregex

If you'd like to use it without requiring it everywhere, you can add it to the list of node globals:

global.heregex = require('heregex');

Questions

How do I make a literal #?

Get rid of any whitespace immediately preceding it. For heregex to consider something a comment, it must have a space before the # or be the first character on a new line. If you need the space or if its the first character on a new line, escape it to \#. \# gets passed through directly as \#. This is not an issue, since an escaped # is still #.

let regex_basic_css_selector = heregex`
    ^\.([_a-z][_a-z0-9-]*)   # classname
  | ^#([_a-z][_a-z0-9-]*)    # id
  | ^([a-z0-9]+)             # type
  ${'i'}
`;

which evaluates to:

/^\.([_a-z][_a-z0-9-]*)|^#([_a-z][_a-z0-9-]*)|^([a-z0-9]+)/i