antlr4ts | Optimized TypeScript target for ANTLR | Hacking library

That can only be done by using target specific code. For example, in Java that would look like this:

Your grammar works pretty well for me (also using the TS runtime in my extension):

Maybe it's something in the input handling, how you load the input? The correct approach is to use the (relatively) new CharStreams:

It was my understanding since FROM is a identifier, it's not a valid field in the select_clause (maybe I'm just misunderstanding)?

All the parser sees is a discrete stream of typed tokens coming from the lexer. The parser has no intrinsic way to tell if a token is intended to be an identifier, or for that matter, have any particular semantic nature.

In designing a fault-tolerant grammar, plan the parser to be fairly permissive to syntax errors and expect to use several tree-walkers to progressively identify and where possible resolve the syntax and semantic ambiguities.

Two ANTLR features particularly useful to this end include:

1) implement a lexer TokenFactory and custom token, typically extending CommonToken. The custom token provides a convenient space for flags and logic for identifying the correct syntactic/semantic use and expected context for a particular token instance.

2) implement a parser error strategy, extending or expanding on the DefaultErrorStrategy. The error strategy will allow modest modifications to the parser operation on the token stream when an attempted match results in a recognition error. If the error cannot be fully resolved and appropriately fixed upon examining the surrounding (custom) tokens, at least those same custom tokens can be suitably annotated to ease problem resolution during the subsequent tree-walks.

I think using ANTLR is a bit of overkill for your task. ANTLR, or any other parsing tool, is good for constructing the structure of a string, but here, you just want to know if a string is an identifier or not. If you really need ANTLR, please elaborate why and then I can help you with the error handling.

For this task, I'd suggest, you just use a regular expression like the following for testing an identifier:

NPM docs state that engines field casts an error only when your package is installed as a dependency:

Unless the user has set the engine-strict config flag, [engines] field is advisory only will produce warnings when your package is installed as a dependency.

As developer/mantainer of the project you should not see any alert coming from your engines field.

Since you need to compile your files when you run npm install only, you might simply use postinstall hook.

Please also note that prepublish is there to stay, it will just change its behaviour on npm@5 by firing only before publish hook.

That's quite surprising. I'm using the same approach like you in my node module antlr4-graps, which has ES6 set as transpilation target and everything is working very well. Take a closer look there. Maybe you can spot other signifcant differences between your code and mine. I assume you have the latest alpha of antlr4ts installed.