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

grass

v1.0.2

Published

A greedy, streaming lexer written in vanilla Javascript

Downloads

365

Readme

Grass

A greedy, streaming lexer written in vanilla Javascript.

Build Status

browser support

Features

  • Fixed memory usage regardless of input size
  • Emits both token type and matched text
  • 100% statement and branch coverage

Streaming Usage

Grass expects an NFA created with finite-automata.


var grass = require('grass')
  , Fragment = require('finite-automata')
  , fs = require('fs')
  , red
  , blue
  , dog
  , rule
  , lexerStream

// Make a DFA that matches /(red|blue)dog/ and labels it 'animalToken'
red = new Fragment('red')
blue = new Fragment('blue')
dog = new Fragment('dog', 'animalToken')

rule = red.copy().union(blue).concat(dog)

fs.createReadStream('input.txt')
  .pipe(grass(rule))
  .pipe(consumer)

// consumer will recieve tuple ['animalToken', match <string>] for every match

Sync Usage


grass.sync(rulea)('reddogredcatbluedog')
// ==> '[['animalToken', 'reddog'], ['animalToken, 'bluedog']]'

Greediness

Say you have a rule like /11*2*3*4*5*6*7*8*9*/. This matches ascending series of digits that start with 1.

Example matches: 1, '1234', '11223', '199'

Grass is greedy. This means that it will try to match as much text as possible, and only backtrack when it has no way to continue.

This means that grass might not emit a match at the end of the stream's data event. Sending an ascending series like 123 to grass will not result in a match until the stream is ended, or a digit lesser than 3 occurs. This is because grass knows that there is a possibility of a longer match, and it will wait for the next data event to decide on the fate of the data in its internal buffer.

This is expected behavior, because if the series 1234 was sent in two parts, 12 and 34, it should only result in one match.