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

trek.js

v0.3.0

Published

A parser and AST builder based on the TPEG variant of PEGs.

Downloads

10

Readme

trek.js

A PEG parsing system in which the AST and parser are described by a single grammar. The constructed parser is then capable of populating the AST directly from source texts.

Example

Parsers can be written using the JavaScript API or compiled from a shortened form.

// first create a parser
var p = require('trek.js').parse

// create a whitespace and comment skipping parser
// p.star(q)  - matches `q' zero or more times, stores a string.
// p.plus(q)  - matches `q' one or more times, stores a non-empty string.
var comment = p.lexeme("//", p.star(p.notChar("\n")), "\n"),
    spacing = p.plus(p.or(p.whitespace(), p.char(comment)))

// trek parsers use the whitespace parser as part of the stream.
var stream = p.stream(spacing)

var idFirst = p.or("_", "$", p.range("az")),
    identifier = p.lexeme(idFirst, p.star(p.or(idFirst, p.range("09"))))

// star/plus on a string/object storing parser allows the space parser
// to match in between elements and stores an array of the contents.
var manyIdentifiers = p.plus(identifier)

var ast = stream.parse(manyIdentifiers, "hello totoro    friend")
// ast now contains ["hello", "totoro", "friend"]

The same parser in short:

Comment         <- "//" ^ (!\n)* ^ \n
Spacing         <- (\s / Comment)^+
IdFirst         <- [a-z$_]
Identifier      <- IdFirst ^ (IdFirst / [0-9])*
ManyIdentifiers <- Identifier+