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
Currently compiler will generate output even if compilation fails. While it is true that it also sets a flag indicating if a compilation failed or not, it makes working with the compiler API harder than it needs to be. For example, while working on a Grunt / gulp plugin, we shouldn't need to generate a file that would output errors in a browser, we should simply break the compilation (fail fast). We can still generate client-side files in the express integration, though.
My proposal here is the following one - let's remove the error-reporting content generation from the compiler and let's move it to a separate class that could be plugged on top of the compiler.
The text was updated successfully, but these errors were encountered:
For info, some time ago, I started doing this change on the compilerErrorHandling branch on my fork: see here. I have not taken the time to finish it yet, but I think it is important to do it.
Currently compiler will generate output even if compilation fails. While it is true that it also sets a flag indicating if a compilation failed or not, it makes working with the compiler API harder than it needs to be. For example, while working on a Grunt / gulp plugin, we shouldn't need to generate a file that would output errors in a browser, we should simply break the compilation (fail fast). We can still generate client-side files in the express integration, though.
My proposal here is the following one - let's remove the error-reporting content generation from the compiler and let's move it to a separate class that could be plugged on top of the compiler.
The text was updated successfully, but these errors were encountered: