It is often a false assumption that MobX can only be used with decorators. That's not true. The article explains how to use MobX in a create-react-app or Next.js application with and without using decorators. There is also one alternative to avoid ejecting when using create-react-app.
There is a high likelihood that there are already a multitude of articles about the new React.js 16 release. But for learning about the changes of the library myself, I wanted to read up all the new React 16 features and improvements too. Maybe it is useful for you if I share briefly what I have learned. In the next days, I hope to find the time to update my articles and course content accordingly to the changes.
The course turned out to exceed all my expectations. What started as an attempt to write a sole ebook about state management in React with Redux and MobX, turned out into a full blown course with a 250-page ebook, exciting applications and boilerplate projects to get started in learning and building applications with these libraries, and screencast series about implementing React applications from scratch with state management.
The article will guide you through using SVG in React. It shows you how to use a SVG logo for your application and how to add SVG patterns in React for your backgrounds. It will demonstrate two alternatives for using SVG patterns in React.
Newcomers to React often start with applications that don't need data fetching at all. Usually they are confronted with Counter, Todo or TicTacToe applications. That's good, because data fetching adds another layer of complexity to your application while taking the first steps in React. However, at some point you want to request real world data from an own or a third-party API.
React with its ecosystem is a flexible framework. You can choose your libraries to complement your React core. The following article will give you an opinionated approach to select from these libraries to build a sophisticated React application.
State management is difficult. A view library, such as React, enables you to manage local component state. But it only scales to a certain point. React is just a view layer library. Eventually you decide to move on to a more sophisticated state management solution such as Redux. Yet there are certain things, that I want to point out in this article, that you should know about React before you jump on the Redux train.
The provider pattern in React is a powerful concept. You will not often see it when using plain React, but might consider using it when scaling your application in React. Basically it takes the clutter away of passing mandatory props, that are needed by every component, down your whole component tree.