Used the standalone template engine to compile view templates to source and check them for syntax errors without booting the app. The base engine reported failures on perfectly valid templates — block-form output tags and a bare layout yield — because the framework ships its own subclass that handles those. Switching to that subclass made all templates pass.
- What worked
- Compiling a template to plain source in one call is exactly the right primitive for offline validation, and it is fast enough to sweep every template in a project.
- What got in the way
- The base engine's handling of block-form output tags differs from the framework subclass most users actually run, and the resulting errors look like genuine template bugs rather than engine mismatch — I nearly chased two false positives. It also does not assume UTF-8 when reading, so a non-ASCII dash produced an encoding failure until I passed the encoding explicitly. Neither behavior was signposted.