Using JavaScript Errors

Dealing with JavaScript or an Ajax based application is always a tricky task. Even the most experienced developers would end up with unexpected errors especially when the application is tested for the first time. Bugs and error in coding will always be there and the possibility of errors showing up after the application has been launched is still there.

For that reason, some developers are opting to provide some error prompt within the application. The error prompt could be easily customized in JavaScript and the message could be as simple as “Page Error Encountered” to outrageous messages such as “Nope, the Function is Not Here.” But whatever the message would be, developers could configure the error message by simply adding another error function.

But is this really necessary?

There’s an ongoing debate regarding the need to add JavaScript prompts for errors. Those who favor in adding JavaScript Error messages claim that the addition of this function will provide additional monitoring tools for developers. As soon as the application receives an error code, the developers could be alerted and if the error is overwhelming, developers could provide a fix as soon as possible.

On the other hand, those who do not favor the addition of JavaScript error prompt site bloating scenarios for the application. Adding functions that will only say something wrong has happened is almost the same as the default error codes in browsers. Besides, some functions in JavaScript is not readable in browsers so configuring the error function per browser is very difficult.

The Framework Scenario

The JavaScript error function could be very useful when you are working with JavaScript libraries and frameworks. These tools are great in building Ajax and JavaScript based applications fast but there are certain functions that might not be covered by the framework and/or the library. For that reason, error codes should be added.

But the dispute in adding error codes again comes back in terms of location of the error codes. The error codes in frameworks and libraries would be beneficial but when they are implemented in deeper levels of the application, monitoring of these functions could easily bloat the application.

Remember that each function should have an error code if the developer wants to actively monitor them. If the error codes are added to the deepest functions, the application would have to deal with error codes more than the actual functions.

Some have recommended that the error functions should only be added in the interface level. But that would only solve half the problem since data interaction is not dealt with. You’ll have different error prompts which will only confuse users.

Special Scenario Only

Although JavaScript error codes could easily bloat the application, there are certain scenarios that JavaScript error could actually become useful. One of those scenarios is when the application is being built by a group and the application is proven to be massive. The help of error especially when they are integrated with error codes will always be there. But if the application is small and developed by one person only, JavaScript errors will take more resources than the main functions.