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

escript-antlr4

v0.2.0

Published

An Escript lexer & parser that provides both visitor and listener patterns to traverse the parse tree.

Downloads

4

Readme

escript-antlr4

Getting started

  1. Install escript-antlr4 and antlr4ts as dependencies using your preferred package manager.
npm install escript-antlr4 antlr4ts --save
yarn add escript-antlr4 antlr4ts
  1. Use your grammar in TypeScript (or JavaScript)
import { EscriptLexer, EscriptParser } from 'escript-antlr4';
import { ANTLRInputStream, CommonTokenStream } from 'antlr4ts';

const program = `
program main(arg0, arg1)
    Print(arg0);
endprogram

function f1() endfunction
function f2() endfunction
`;

const inputStream = new ANTLRInputStream(program);

const lexer = new EscriptLexer(inputStream);
const tokenStream = new CommonTokenStream(lexer);
const parser = new EscriptParser(tokenStream);

/**
 * Parse the input:
 * 	- A source file (.src or .inc) has entry point `compilationUnit`.
 *  - A module file (.em) has entry point `moduleUnit()`.
 */

const tree = parser.compilationUnit();

The two main ways to inspect the tree are by using a listener or a visitor, you can read about the differences between the two here.

Listener Approach
// ...
import { EscriptParserListener, ProgramDeclarationContext } from 'escript-antlr4';
import { ParseTreeWalker } from 'antlr4ts/tree';

class EnterProgramListener implements EscriptParserListener {
    enterProgramDeclaration(context: ProgramDeclarationContext) {
        console.log(`Program name: ${context.IDENTIFIER().text}`);
        // ...
    }

    // other enterX functions...
}

// Create the listener
const listener: EscriptParserListener = new EnterProgramListener();
// Use the entry point for listeners
ParseTreeWalker.DEFAULT.walk(listener, tree);
Visitor Approach
// ...
import { EscriptParserVisitor, FunctionDeclarationContext } from 'escript-antlr4';
import { AbstractParseTreeVisitor } from 'antlr4ts/tree';

// Extend the AbstractParseTreeVisitor to get default visitor behaviour
class CountElementsVisitor
    extends AbstractParseTreeVisitor<number>
    implements EscriptParserVisitor<number> {

    defaultResult() {
        return 0;
    }

    aggregateResult(aggregate: number, nextResult: number) {
        return aggregate + nextResult;
    }

    visitFunctionDeclaration(context: FunctionDeclarationContext): number {
        return 1 + super.visitChildren(context);
    }
}

// Create the visitor
const countElementsVisitor = new CountElementsVisitor();
// Use the visitor entry point
const count = countElementsVisitor.visit(tree);
console.log(`There are ${count} function declarations`);