Jest 14.0: React Tree Snapshot Testing, Progressive loading for modern web applications via code splitting, and React.js in patterns
One of Jest's philosophies is to provide an integrated “zero-configuration” experience. The Jest team wants to make it as frictionless as possible to write good tests that are useful. They observed that when engineers are provided with ready-to-use tools, they end up writing more tests, which in turn results in stable and healthy code bases.
Your users tired of waiting for your app to load? Speed up that boot time with progressive loading.
There are many different kinds of patterns used in React. Luckily, the community has seemed to settle on a few as of late, but that doesn't mean knowing the lesser used ones aren't valuable.
A step-by-step TDD approach on testing React components using Enzyme.
Most of the solutions for dependency injection (DI) in React components are based on context. The famous connect function and the Provider there use the context. However, the React development team recommends avoiding the usage of the context. In this article This article talks about how we can use InversifyJS as a context-free solution for DI in React applications.
React's key design decision is to make the API seem like it re-renders the whole app on every update. This makes writing applications a lot easier but is also an incredible challenge to make it tractable. This article explains how with powerful heuristics we managed to turn a O(n3) problem into a O(n) one.
The React team have just released Create React App. It’s a quick and simple way to get started with a single-page React application. While it's a popular tool already, there are some big features it is currently not implementing, like hot module replacement (HMR).
As opposed to create-react-app tool released by Facebook, React App SDK is shipped with a bunch of useful tools commonly used in the front-end community — Redux, CSS Modules, HMR, React Hot Loader, code splitting, async chunk loading and more.
An interesting look at a super tiny vanilla Flux implementation.
Richard's talk is not an introduction to React, or an explanation of Backbone. Instead it’s an exposé of the “aha” moments that using React has led to, that are the difference between good and bad code.