frontend Advanced Redux TDD: Reducers We do TDD for most development at Transparent Classroom, including our frontend business logic written in Redux. Doing TDD for Redux revealed certain frustrating aspects of structuring and testing Redux. I set out to make it better. This post offers a slightly different structure
web bundling Ramda, webpack, and tree-shaking. Are you using Ramda and Webpack? Then you probably want to read this, because chances are good you're importing more of the Ramda library than you might think... We're all big on reducing bundle sizes for the web. When leveraging larger utility libraries such
frontend Neat features of Flow. I recently took a couple hours to read through the Flow docs, which was an informative and valuable use of time. Here are a bunch of notes on useful and slightly intuitive aspects of Flow. Many of these code blocks are pulled from the
testing Jest + Chai and expect.assertions. At Transparent Classroom, we use both Mocha/Chai to test our modules and Redux code and Jest to test our React components. Mocha/Chai and Jest are very similar in syntax, except for this annoying difference in that the matchers are different, e.g.
frontend Source maps for Sentry: setting the UTF-8 encoding. We use Sentry at TransparentClassroom to monitor errors in our front-end application. It's an excellent tool and has proven very useful, but for the longest time we could not get source maps to work correctly. As a consequence, we'd get woefully useless errors like