Here are some reads I found this week: A Pattern For Cancelling Fetch API Requests - how to cancel fetch Create a user controlled dark or light mode - design accessible dark and light modes for your website Computer Architecture - Fall 2019 Course - free YouTube lectures from ETH Zürich Commit Message Driven Development - you might have heard of README Driven-Development, but what is Commit Message Driven Development?
Raise your hand ✋, if you’ve seen this error in your React application: Warning: Can’t call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method. The Problem This error often happens when you make an asynchronous request for data, but the component unmounts. For example, some logic in your app tells React to navigate away from the component.
I wrote about my Gatsby build time woes yesterday. Unfortunately, Netlify and Gatsby rebuild my site completely with every update. I use the gatsby-plugin-netlify-cache but build times are still high. While searching for ways to optimize my Netlify build I stumbled upon an issue on the Gatsby repository. The issue was merged into master and published to firstname.lastname@example.org. Before: At the moment this hash changes if anything within ./src has changed between builds.