First look at the ecosystem of packages related to React. At the beginning of Facebook's build React, there were a number of packages from third-party libraries in the open source community. These packages use React to supplement other features to provide a complete application solution. Of course, there are competing relationships in the installation package that provide similar functionality.
A common feature of rich WEB applications is the availability of multiple "routes". These "routes" are essentially different blocks of functionality that behave as separate URLs in the browser. React does not need to use routing for simple applications, and routing is not required in some desktop and mobile application environments. Therefore, although React Router is the most popular routing solution for React applications, React Router is only half as popular as React.
Developers of React know that React is applied to a well-defined problem area and has a well-defined interface, which makes it possible to apply itself to a wider range of applications than originally designed. This approach, while increasing the pool of developers using React, has further enhanced the React, extending the React ecosystem and creating a useful cycle. React, as a part of the solution, is inherently less convenient to use than a complete framework such as Ember and Angular.
React as a non-complete solution, one of the unresolved issues is the data-tier portion of the application. When introducing React, Facebook also introduced Flux, a way to manage state in the application, and GRAPHQL, a system for communicating between the client and the server. Neither of them is as popular as the React itself.
Flux was introduced shortly after React, but it was not popularized until the middle of the 2015. During this time, flux and React Router together in a synchronous upward trend, which also shows that flux and React Router are in use in network applications. However, after the middle of 2015, the trajectory of flux and React Router has been greatly differentiated, flux in the popularity of the slow decline.
One cause of Flux's popularity decline is the rise of Redux. Redux and flux are for the exact same part of the application function, Redux was launched in the middle of 2015, and the usage rate increased rapidly, while Flux began to decline gradually at the same time. Redux is now nearly as popular as the React Router, and the two are closely related and increasingly popular. This also indicates that Redux has replaced Flux as the preferred state management system in React network applications.
MOBX was launched in mid-2016 and is a competitor to Flux and Redux. Although the use of MOBX is not high, but is now growing rapidly, it is worth attention.
RxJS is another competitive state management component of Flux and Redux. The prevalence of RxJS is not statistically good. First, RxJS has two existing versions, one is the traditional version of Rx and one is the current version RxJS. The download volume of these two versions is large, with Rx downloads declining while Rxjs downloads are growing.
The use of RxJS is essentially a driver for other project dependencies, especially for the Angular CLI. This means that all drives that use Angular need to use the same RxJS. At the same time, RxJS is also incorporated into some other popular command-line tools.
GRAPHQL and React were developed by Facebook at the same time, but there was no intrinsic connection between the two. GRAPHQL is a way for WEB clients to query server data. GRAPHQL has gained popularity through two competing libraries called Relay and Apollo, Relay and Apollo provide a WEB application for generating graphql and managing data flows.
Relay was first released and growing, but after six months the release of Apollo rose faster, and it was increasingly popular, and the pace of growth was accelerating significantly. Although the absolute number of GRAPHQL developers is still small, the growth trajectory of Apollo means that GRAPHQL is well worth the attention of developers.
React Eco-System Overview
Through the 12-month change trend of the React ecosystem, the following conclusions can be obtained:
apollo 's usage rate is growing rapidly.
flux The use rate is declining.
react Router and Redux are very popular and have a strong connection in use.
MOBX has good growth, But its utilization rate is far from reaching Redux.
react The ecosystem itself is enormous.
Reproduced please specify from: Grape City control
about Grape City
the movable lattice is developed, marketed and provided with technical services by Grape City Company. Founded in 1980, Grape City is the world's leading software and service provider for development tools, business intelligence solutions, and management system design tools. Xi ' An grape city is its branch office in China, providing software research and development services for the global market, and providing international advanced development tools, software and research and development consulting services for the informatization of Chinese enterprises.