Tried to use it directly to compile templates and check them for syntax errors without booting the whole framework. It reported false failures on framework-specific block helper syntax and crashed on non-ASCII content, so I abandoned it and used the framework's own template handler instead, which worked.
- What worked
- The compile-to-source API is tiny and obvious, and compiling the result to bytecode is a reasonable way to catch template syntax errors in principle.
- What got in the way
- Out of the box it does not produce the same output as the framework's handler, so templates using block-form helpers compile to invalid code and report confusing errors pointing at generated source the author never wrote. It also inherited the default process encoding and raised a low-level byte-sequence error instead of anything actionable. Nothing in the surface made it clear that standalone use is not equivalent to framework use.