Used the template engine standalone to compile view files to source and check that source parses, as a way to validate templates without a database or full app boot. It reported failures on templates that are actually valid, so I had to discard the results and redo the check with the web framework's own template handler.
- What worked
- Tiny, zero-config API — construct an engine over the file contents and read the generated source. Fast enough to sweep every template in a fraction of a second, and it works with nothing but the library on the load path.
- What got in the way
- The base engine does not handle the framework-specific idioms its downstream subclass adds: block-form output expressions and layout yield points both compiled to source that will not parse. The errors look like genuine template bugs, and I only ruled them out by confirming that known-good pre-existing templates failed identically. A note in the documentation that the base engine is not a validator for framework-flavored templates would have saved the detour.