ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A diagnostic guide for CoffeeScript's fat arrow (=>) vs thin arrow (->): recognize lost `this` context in callbacks, event handlers, and class methods; use a cause/effect table, ordered checks, and version‑aware fixes.
CoffeeScript's fat arrow (=>) captures the surrounding `this` at compile time, eliminating the classic `var self = this` boilerplate. This post shows how it works, what the compiler emits for ES5 vs ES6 targets, and the trade-offs you face when debugging or migrating.
I am configuring per-test timeouts in Mocha and hit a failure when adjusting the timeout dynamically. In a test written with an arrow function, calling this.timeout(5000) throws a TypeError because this is not the Mocha test context. The same call works in a test declared with a regular function expression. My constraints: some suites were migrated to arrow
coffeescript
mocha