Catch and process possible exception on JSTransformer compileAsync and renderAsync #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similarly to problem resolved by #20, because of uncached exception of JSTransformer compileAsync and renderAsync functions, the real problem does not output to console:
After applying this pull request in output we get more useful information (and correct exit code):
This exception throw because of
include:markdown-it _idea.md
Including Plain Text construction inindex.html.pug
.After some investigation of the reason that async function throw exception I found next line in jstransformer implementation. So yes, it seems jstransformer issue, but looking at the date of its last release and count of unresolved issues, I think it will be easy and faster to fix it here.
In future, if the issue of compileAsync and renderAsync methods will be fixed this try/catch blocks could be deleted.