I ran into a situation today where my build started failing and the the only console output I got was:
[✔] Gathered content to be generated
Static site generation failed.
After digging in I found that any GenerationFailedException thrown inside a build task's closure is ignored and only the closure's return value is captured by the calling method.
I updated the task closures so that they will now return an exception message instead of throwing, then the calling method (createContentFiles), will check for an exception message in the results and throw an exception from outside a task loop.
With this change the build output will now appear like this:
[✔] Gathered content to be generated
[✘] /page (Exception message here)
Static site generation failed.
This PR prevents exception messages from being swallowed by build tasks.
My SSG config is set to fail on errors:
I ran into a situation today where my build started failing and the the only console output I got was:
After digging in I found that any
GenerationFailedExceptionthrown inside a build task's closure is ignored and only the closure's return value is captured by the calling method.I updated the task closures so that they will now return an exception message instead of throwing, then the calling method (
createContentFiles), will check for an exception message in the results and throw an exception from outside a task loop.With this change the build output will now appear like this: