React.js

Unlike most front-end web frameworks, React's aim is to solve the various challenges of building user interfaces that rely on changing data. Although React is a simple JavaScript library and is easy to get started with, it is still possible to misuse it in ways that deny the web app from reaping the benefits that React has to offer. In this article, Toptal engineer Ivan Rogic demonstrates the synergy of React, Redux and Immutable.js, and shows how these libraries together can solve many performance issues that are often encountered in large web applications.

Using React.js props your application's front-end. In particular, testing user interactions and viewing renderings is vastly improved with React UI testing.

In this article, I'll go through some of the interesting features and libraries that are available to use with React. Even if you don't plan on using React, taking a look at its ecosystem is inspiring. You may want to simplify your build system using the powerful, yet comparatively easy to configure, module bundler Webpack, or start writing ECMAScript 6 and even ECMAScript 7 today with the Babel compiler. So, let's explore the React ecosystem!

This article provides the overview of pain points caused by AngularJS and reasons for switching to React.

One of the biggest and most common problems in front-end web development is state management. A developer is constantly focused on keeping the state object in sync with its view and the DOM representation. Users can interact with the application in many ways and it's a big task to provide a clean transition from one view state to another. We will see how using React JavaScript library can help us reduce application complexity and offload UI transitions from our application.

React.js is a fantastic library. It is only one part of a front-end application stack, however. It doesn't have much to offer when it comes to managing data and state. Facebook, the makers of React, have offered some guidance there in the form of Flux. I'll introduce basic Flux control flow, discuss what's missing for Stores, and how to use Backbone Models and Collections to fill the gap in a "Flux-compliant" way.