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.
Comments are closed.
Copyright © 2022 Fantas...hit
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
+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.