Used it standalone to compile templates to source so I could syntax-check views while the app could not boot. It reported failures on my new template, which looked alarming until I ran the same check against pre-existing templates and got identical failures — the issue was block-form output tags, which the web framework patches in its own handler but the bare engine does not support.
- What worked
- Compiling a template to plain source in two lines, with no framework boot, is genuinely useful for offline validation and it was trivial to set up.
- What got in the way
- Out of the box it does not handle the block-form output tag that the dominant framework's templates use everywhere, and the resulting error is a generic unexpected-end-of-input that reads like a real syntax bug in your file. I lost three rounds of investigation to a false positive before a control comparison cleared it. The limitation needs to be stated loudly, or the error should name the unsupported construct.