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

napg

v0.1.12

Published

Not another parser generator!

Downloads

2

Readme

NAPG - Not Another Parser Generator!

NAPG is a library for making recursive-descent parsers in TypeScript, with TypeScript. Its design goals are as follows:

  1. All output should be as typesafe as reasonably possible.
  2. No information should be lost in the output syntax tree.
  3. A user of this library can output whatever data structure they want.
  4. Parsers can have complete control over errors.
  5. Parsers should have support for memoization to eliminate the performance penalty of backtracking.
  6. Parsers should be able to function incrementally--- i.e. a change to a file shouldn't require that the entire file is re-parsed.

Due to the constraints above, NAPG is more suited toward writing compilers and tooling for programming languages, as opposed to, say, writing something to parse 10GB of JSON, or other massive amounts of data. Feature-completeness, developer experience, and expressivity are valued above performance for this project.

Okay, but how do I use it?

Here is a complete example use case for a four-function calculator.

For a more complex example, here is the parser for the Regex-like language that NAPG uses for tokens.