npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




Import other PEG files into a PEG.js grammar.






Import other PEG files into a PEG.js grammar.

Forked from casetext.


npm install --save pegjs pegjs-import


pegjs-import provides a single function that replaces peg.buildParser:

  var pegimport = require('pegjs-import');

  var parser = pegimport.buildParser('path/to/grammar.peg', options);

Instead of taking a string, it takes a filename.

Inside a PEG.js grammar, you can now make use of the @import directive, like so:

/* NOTE: this grammar won't work in stock PEG.js anymore! */

  this.notes = "Initializers work as you expect them to and are imported.";

@import "path/to/grammar"

  = grammar

When you @import another grammar, that grammar's topmost rule becomes accessible in the context of the current grammar under one of two possible rule names:

  • A name you provide explicitly through the use of the optional "as" parameter
  • The basename of the file, corrected to be a valid Javascript identifier (so if the file were called /foo/bar/my-grammar.peg, the rule name would be my_grammar).

Changes from stock PEG.js behavior

  • You cannot supply options.allowedStartRules anymore. The only allowed start rule is always the first rule in the grammar.
  • You cannot supply a grammar as a string, you must give a filename. There are libraries that provide virtual and in-memory filesystems if you want to work on grammars as strings.


  • pegjs-import is only tested on NodeJS, though the parsers work everywhere they usually do.
  • Circular dependencies explicitly throw an exception. Don't use them.
  • Please don't do funny things with rule names, pegjs-import will probably explode. I will not be held responsible for exploding grammars.



  • Fixed a bug in path comparison that broke Windows.


  • parse-imports now handles /index.peg correctly.


  • Resolve a glitch in external rule name resolution.


  • Don't require "as" identifiers to have two characters in them


  • Make sure we treat internal vs. external rule_refs correctly


  • Fixed bug in options parsing.


  • Changed syntax to more closely correspond to that of PEG.js.