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

cheddar-parser

v0.4.0

Published

The parser for Cheddar

Downloads

4

Readme


Installation

Install the CLI (includes REPL) using:

$ npm i -g cheddar-parser

Install for your project using:

$ npm i --save cheddar-parser

Usage

CLI

Simply running cheddar-parser will open up a REPL. Otherwise, if not a TTY, STDIN will be used as input to STDOUT. Various output formats exist, through flags.

--ast: Outputs an AST. Best for manually reading the parse tree --obj: Outputs an object. Provides in-depth data such as index & state --json: Outputs a JSON. Best for processing through another program --pretty: Pretty prints outputs. This includes syntax highlighting result & indenting JSON. Automatically assumed on the REPL.

In Node.js

One installed simply access the given parser using:

require('cheddar-parser/dist/path/to/item')

Alternatively, most common parsers are available through simply the module itself. example:

require('cheddar-parser').Expression

The full list of parsers is here.


To use a parser simply do:

let parserInstance = new parser(code, startIndex);
let result = parserInstance.exec();

result may be an instanceof CheddarLexer (ches.Lexer), in which case it succesfully parsed, a string, in which it errored, the string is the error description, or a symbol, in which it is a symbol which represents the given error.

An example, of the most common way a cheddar lexer is used:

let run = new parser(code, 0);
let res = run.exec();

if (!(res instanceof ches.Lexer)) {
    // Error, propogate the error
    return `Syntax Error: ${res} at ${run.Index}`;
} else {
    
}

You can also use the ches.Helper.Locate(code, index) to retrieve an array of [row, col, index] of the index in the code.