- Fixes noelforte#422
This dramatically improves error messages in most cases, including
a line-level pointer to which part of the template ran into a problem.
Uses vento's built-in methods to do that.
There _is_ a printError method in Vento but this uses stringifyError
instead to play nice with Eleventy's expectations of a function
that throws an informative error: we want to log via Eleventy
instead of directly printing to `console.error`.

mentioned this pull request

Closed

noelforte added a commit that referenced this pull request

Reimplements `stringifyError` with Eleventy-specific considerations, since Eleventy formats the error stack and error messages by default