Avoid Common Node.js Pitfalls: DecodeURIComponent, Promises, and HTTP Errors

When developing with Node.js, developers often encounter hidden pitfalls that can crash applications or cause subtle bugs. Below are several common issues and how to fix them.

decodeURIComponent

Encoding URL parameters with encodeURIComponent is common, but decoding with decodeURIComponent is not safe; malformed sequences throw exceptions. Wrap the call in try { decodeURIComponent(str); } catch (e) { /* handle */ } to prevent the process from exiting.

Promise

Promise vs. callback

When a callback throws an error, the surrounding .catch() can capture it and inadvertently invoke the callback again, leading to confusing behavior. The recommendation is to avoid mixing promise‑based implementations with callback patterns.

If the original function is promise‑based and you want to support callbacks, it’s better to abandon that idea.

Promise vs. catch

Wrapping a third‑party promise API (e.g., request(url, options).then().catch()) and swallowing errors in the catch block prevents the caller from seeing failures. After logging the error, re‑throw it so the original API’s error flow remains intact.

http

Using the built‑in http.get without error handling works initially but will crash the app when network errors occur. Always attach an error event listener, e.g., require('http').get(url).on('error', function () {});, to keep the process alive.

Conclusion

Node.js development contains many subtle traps—decodeURIComponent misuse, hidden Promise errors, and unhandled HTTP exceptions. Being aware of these issues and applying proper error handling will make your applications more robust.