You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some kind of issue with my templates causing a render error.
Eleventy advises using debug mode even though I'm already using debug mode. I presume it shouldn't give this advice when in debug mode.
As an aside - the output can be hard to skim to work out which file has the issue. Most of the errors spat out refer to node modules, rather than the likely culprit files. In this case, it took quite a long time to work out what was wrong as the actual file with the issue isn't stated. All it tells me is it's line 3 of some file. I went through all recently changed files moving the lines down by one to work out which file was causing the crash.
The text was updated successfully, but these errors were encountered:
Fair point! Some of the error reporting stuff has been already reworked and improved in 0.5.4 but I’m sure it still says this 😎
The debug output tries to give as much information as possible for both you and I to debug the situation. That means that yes, the debug output will spit ugly stack traces—maybe not super helpful to you but they’re necessary.
Hopefully it will read a little better in the next version, we can revisit discussion after that’s released.
I have some kind of issue with my templates causing a render error.
Eleventy advises using debug mode even though I'm already using debug mode. I presume it shouldn't give this advice when in debug mode.
![screen shot 2018-09-12 at 13 00 31](https://user-images.githubusercontent.com/2204224/45423641-daa8b900-b68b-11e8-933a-6764c62b743e.PNG)
As an aside - the output can be hard to skim to work out which file has the issue. Most of the errors spat out refer to node modules, rather than the likely culprit files. In this case, it took quite a long time to work out what was wrong as the actual file with the issue isn't stated. All it tells me is it's line 3 of some file. I went through all recently changed files moving the lines down by one to work out which file was causing the crash.
The text was updated successfully, but these errors were encountered: