New Point Release

Fixed bug #8

Also, releases will no longer be marked as pre-release. They are fine to be used where standard antlr4 and antlr4ts were used before.

New Point Release

This release contain mostly internal changes. The antlr4ng-cli tool dependency has been updated to the latest version and build + test processes has been improved (esbuild instead of webpack, Jest instead of Jasmine).

There are also some smaller fixes in Interval and ParseTreeVisitor. The latter now has the same implementation as the Java runtime.

New Minor Release

This release includes a lot of cleanup.

• Generated parser rules that can appear as either returning a single parse context or a list of that no longer use the __list() appendix in their name. Instead method overloading is used now to distinguish between the two cases.
• The members getTypedRuleContext and getTypedRuleContexts have been renamed to getRuleContext and getRuleContexts respectively, just as in the Java runtime.
• There are more renames (_errHandler -> 'errorHandler, _input->inputStream` and more).
• The package has been stripped down to just a single bundle file. This is an ESM module now, so it can be used in both, node and browser environments. No differentiation is made anymore between the two.
• The internal folder structure has been changed to match the Java runtime.
• Extended some classes, added new type definitions and exported some more classes.
• Improved BitSet to use less memory.

v1.0.6

This release contains a number of bug fixes that show up only under certain circumstances (manual token creation, XPath use).

Fixed some issues

I'm actually working with the new package in a large project and fixed a number of issues found while migrating from antlr4ts.

Initial Release

Out of the need to have a well working ANTLR4 runtime, which includes at least TypeScript type definitions, this package was created.

Note: to work out of the box this runtime needs parser files generated with an updated ANTLR4 tool jar, which is not yet available here. Will be in one of the next releases. Meanwhile you can use ANTLR4 4.13.1 and manually update the generated files, if you are in real need.