Can we provide a better user experience for errors in macros?

[joelanman]

If we start recommending macros over html for prototyping, one downside is that small mistakes in macros will crash the kit and give a very technical error message, for example:

(/Users/joelanman/projects/govuk-prototype-kit/docs/views/tutorials-and-examples.html) [Line 10, Column 6] parseAggregate: expected comma after expression

whereas small mistakes in html will just mean rendering errors.

Can we improve this situation for users? For example by detecting these errors and providing a more useful and less daunting message