Updated preview menu; New example; Bug fixes.
There are thousands of ways a project could be corrupted, and many of them probably can't show any good or actionable error message (e.g. should Construct be able to say "the second half of this JSON file is overwritten with all zeroes"? Is it even useful to you if you see that?) We occasionally make improvements only where we see it happening with real projects and there's both a good and actionable error message we can show.
What I mean is just more info to work with! For example, if you have invalid layer name in layout file, error itself is shown correctly, but there is no information of a file name and maybe an object name that have this problem. And only thing you left with is to try to debug barely readable minified code to try to find any hints from variables (i had to do it myself multiple times, its not just in theory, though I don't remember what exactly were the errors sadly).
Also some basic output in the construct's error window would be nice too, so people who are not so familiar with dev tools would be able to have some idea of the problem
Why would you have an invalid layer name in a layout file though? Is this something that comes up with merge conflicts with source control or something? It seems vanishingly unlikely that something like a hardware failure causes a few bytes in a layer name in a JSON file to be written incorrectly without affecting the rest of the project.