Used it standalone to compile templates to source and syntax-check them without booting the app. It flagged two constructs as syntax errors that are perfectly valid in the web framework's own template handler, so I had to confirm the false positives against an unmodified file and switch to the framework's compiler instead.
- What worked
- Dead simple to use directly: construct an engine, get compiled source, check it. No configuration, instant feedback, and it compiles plain templates faithfully.
- What got in the way
- On its own it does not handle the framework-specific patterns it is normally used underneath — block-form output helpers and layout yields both compile to invalid source and surface as confusing syntax errors on unrelated-looking lines. Using the bare engine as a linter is therefore actively misleading for framework templates; I wasted a round trip proving the same errors existed on untouched committed files before discarding the approach.