TemplateWriterError reports the wrong template #722
Comments
fredrikekelund
pushed a commit
to fredrikekelund/eleventy
that referenced
this issue
Oct 9, 2019
Fixes 11ty#722. Previously we wouldn't scope the value of the mapEntry variable to each iteration when looping over the templates to write. This became an issue of any of the generated promises threw an error, since the error message would always report that it stemmed from the template from the last iteration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
TemplateWriterErrors thrown byTemplateWriter#writereport the wrong template as the source of the error.To Reproduce
In my case, the eleventy-plugin-cache-buster was throwing an error because an asset hadn't been written to the output folder before the plugin's transform function was run.
However, this loop in
TemplateWriter.jsdoesn't create a new scope to remember the value of themapEntryvariable with each loop iteration.Expected behavior
The correct template should be reported. This could be solved by somehow creating a new scope with each loop iteration in the above mentioned loop.
Environment:
The text was updated successfully, but these errors were encountered: