node package manager

antlr4-graps

antlr4-graps

NPM

Build Status

ANTLR4 graps (Grammar Parsing Service) is a TypeScript node module using the TypeScript ANTLR runtime (antlr4ts) created by Sam Harwell. At the time being this runtime is still considered alpha, while it works already quite well.

Features

At its core this module manages source contexts for each ANTLR4 grammar source an application provides (usually files, but can also be strings in memory). It manages grammar dependencies and automatically loads them as required (either from the same folder as the requesting grammar or from a common lib folder).

A context is identfied by a unique string, which is usually the absolute file name, but can be any unique string (e.g. a UUID). Using a file name has the advantage that the module can load file content transparently, if no grammar code is given as string (especially important for dependencies).

The module comes with jars for parser generation (the main ANTLR jar and a derived one only for typescript) and can so generate all parser and lexer files for you (targets: Java, C++, C#, JS, Python, Typescript, Swift, Go). It will then parse all error messages and provide diagnostic informations, if problems were reported. Additionally the module does its own syntactic and semantic checks and can so provide a subset of the diagnostics available from ANTLR. These are provided on each reparse call, while ANTLR diagnostics are only available after a generation call (in this case the interal diagnostics are replaced by the external ones).

Here's a feature summary of the module:

  • semi-automatic grammar management (manual loading/unloading of a main grammar, automatic loading of dependencies)
  • (re)parsing of a grammar (and its dependencies), which collects internal diagnostics
  • symbol lookup at a given position, rule name from position, enclosing range (the outer rule or the block containing a symbol)
  • listing of all found symbols
  • syntactic and semantic diagnostics (e.g. duplicate symbols, unknown symbols)
  • symbol reference counts (usage counts), unreferenced rules
  • a reference graph for all symbols
  • code completion candidates (fairly stable now, might be a bit slow for large grammars)
  • railroad diagrams for rules
  • parser generation, including interpreter data generation, with flexible configuration (listeners, visitors, search/lib folder etc.)
  • full semantic checks and reports by code generation (e.g. left-recursive rule detection etc.)
  • built-in interpreters for parse runs without the need to compile the generated parser (not yet finished)
  • ATN graph (nodes and links describing the ATN structure for a given rule)

Usage

You can find details about use and all available public functions and structures in the api reference file.

Testing

The GIT repository contains a test setup, which allows to run unit tests (via mocha). Simply execute:

npm test

Additionally, there is a mocha setup for Visual Studio Code, which even allows to debug the tests. Tests are however not shipped in the published node module.

Known Issues

see bug tracker

Also, the code completion feature is not fully ready yet and needs some improvements. Use it only for testing small grammars for now.

What's next?

  • Improve code completion
  • Automatic code formatting
  • Refactoring: extract rule, rename items, comment selected lines, remove left recursion
  • Templates (for frequently used rules like whitespace, ID etc.)
  • Support for debugging

I'd love to see code contributions, to make the module evolve quicker.

Release Notes

For release details see Git commit history.