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

@kaoscript/parser

v0.7.0

Published

Parse kaoscript files and generate an abstract syntax tree

Downloads

2

Readme

@kaoscript/parser

kaoscript License NPM Version Dependency Status Build Status CircleCI Coverage Status

Parse kaoscript files and generates an abstract syntax tree.

Documentation available at kaoscript.

Evolution

  • July-August 2016: since I didn't wanted to handwriting the parser, I've used a LL(*) parser. Slow since lot of backtracking.

  • August 2016 - May 2017: I've used Jison to generate a SLR parser. Faster (10x) but the syntax was getting complex and tricky.

  • May 2017: I've tried chevrotain (a fast LL(4) parser).

    I didn't choice it because:

    • You have to distinguish ambiguous rules, complexify the syntax
    • You can't switch the tokenizer when parsing
  • May 2017 - *: Handwritten parser. It's basically a LL(1) parser with few lookheads.

    Advantages:

    • at least 2x times faster than Jison
    • manageable code
    • better support of space
    • macro

License

MIT © Baptiste Augrain