Even when launching from the command line, any JS error occuring in main.js is internally trapped, preventing debugging. Instead, you get the following:
The error is not reported in the console.
Filtering out the most rated answers from issues on Github |||||||||||_______|||| Also a sharing corner
Even when launching from the command line, any JS error occuring in main.js is internally trapped, preventing debugging. Instead, you get the following:
The error is not reported in the console.
+1 This is a bug – an incorrect require statement isn’t really the same as an invalid app, which makes this error deceptive at best.
The attached commit seems to just manually detect when a module isn’t found and then still throw the same error, regardless. Is there something I’m missing? It seems like what you want to detect is if one of the key modules is missing (ie main.js), but this looks to report the same error regardless of which require statement goes wrong.
Absent of a more in-depth solution, could the error message be modified to mention require statements in some way? This can be a pain in the neck to debug if you don’t already know that a script error can trigger this.