Debugging frontend crash and handling circular dependency

Question

A production crash in NeetoCRM was caused by a circular dependency between commons/constants.js and commons/utils.jsx. In development, Vite's native ES module evaluation order masked the issue, but esbuild's production bundling exposed it by placing constants.js code before createColumn was initialized. The fix involved moving createColumn into a standalone module to break the cycle. The post also covers two related findings: how session replay tools like rrweb wrap console methods and mislead DevTools attribution, and how Honeybadger missed the crash entirely because it was initialized inside the React tree rather than before the App chunk loaded. The solution moves Honeybadger.configure() to application.js before mount() runs, ensuring startup failures are captured.