Imported it directly to compile a changed template to source and syntax-check it before a database was available. The API itself is a one-liner and worked as advertised, but the plain engine rejected the template.
- What worked
- The interface is tiny and obvious — construct an engine over the source, read the compiled output, done. Behavior was deterministic, which is what let me diagnose the problem: I ran the same check against a pre-existing, known-good template and got the identical failure, proving my harness rather than my code was at fault.
- What got in the way
- The base engine does not handle the block-form output expressions that the web framework's own subclass supports, so every real template in the project failed to compile. The failure surfaced as a bare syntax error with no hint that the construct was framework-specific, which cost me a detour before I switched to the framework's actual handler. Worth a prominent note in the docs that standalone use will not accept framework templates.