Error reference

unterminated_comment

Raised by the parsing engine, so any grammar can produce it.

Message

unterminated comment: {src}

Hint

This comment is never closed.

{placeholders} are filled from the failing token and the details the grammar attached. The wording is informative and can change between releases — the code is the contract. It is what both the TypeScript and Go runtimes guarantee.

Declared by

  • @tabnas/xml — XML 1.0 parsing for the tabnas engine, with namespaces and entities. source npm

The message text for a plugin code lives in that plugin's own error catalogue, alongside its grammar — this page does not copy it, so it cannot fall out of step with the package you are running. The plugin's AGENTS.md lists what raises each of its codes.

What to do with it

  1. Read the rest of the diagnostic: row/col point at the input, expected lists the tokens that would have matched, and ruleStack shows how the parser got there.
  2. Reproduce it on its own with tabnas diagnose --json, which prints the whole object.
  3. Work the grammar back from the failing alternate — the debug-parse skill is that procedure written out, and the errors guide covers raising good ones from your own grammar.

Generated from the engine's error registry . Engine 0.8.10.