ReactJS combines the speed of JavaScript with unique rendering capabilities to make applications that are highly dynamic, performance oriented, and responsive to user input. State of JS report 2018 cites performance as the major reason ReactJS has gained so much popularity in such a short time. When it comes to options for building single-page applications (SPAs), React delivers performance advantages over Angular and other JavaScript frameworks and libraries.

One thing I love about working at OpsRamp is how we always come together to figure out new ways to manage complexity or achieve difficult development goals. Take, for example, managing application states. It’s historically one of the biggest challenges in front-end development. We’re a lean team, so we needed to figure out a better way. In this article, I’ll address how we accomplish this with React at OpsRamp, and how you can apply some of these practices in your own workday.

The article, Serverless API with ReactJS, was first published on the Serverless Guru website. Let’s build a Serverless REST API for our ReactJS website! In my last article, Deploy ReactJS App with S3 Static Hosting, we discussed hosting a simple React app on AWS with S3. This works great for simple static pages but what if you want to do something more? How do you host your API on S3?

At FireHydrant we use Redux Form for all of our forms. It is extremely easy to build complex form logic with all sorts of added bonuses that make using it in our React/Redux front end a no brainer. However, when we started using React Select for our select fields we started running into some issues. You are likely running into some of the same issues we did and so this blog post will help get you off the ground and integrating these two libraries together.

In this blog post we will go through how you can create plugins for Grafana using ReactJS. This presumes you have some basic knowledge about writing components in React.

Back in the days of the wild wild web (www) and post JQuery era, one web framework stood above all others: AngularJS. A “ring to rule them all”, AngularJS consolidated quite a few micro-frameworks and provided many extensibility points of expansion if needed. Over time though, many performance and architectural questions began to arise, to the point of no return – when the guys @Google decided to migrate from AngularJS to Angular (a poor naming decision).

This post is going to be a tad different and longer than what you are used to but I promise, it’s going to be an interesting one. We are going to build a serverless React + GraphQL Web app with Aws amplify and AppSync.

About two years ago here at Mattermost, we decided to start building a prototype for our mobile apps in React Native (RN for short). We were so impressed with how easy it was to build our app for both platforms that we ultimately decided that RN was the way to go for mattermost-mobile apps. Thanks to RN, we can focus exclusively on ensuring feature parity between our mobile apps and our webapp.

React Native has recently gained popularity among the mobile app developer community due to its cross platform compatibility, quick development cycle and better user experience. It is easier to develop, build and maintain apps using React Native.

React 16 introduces bunch of features, most interesting one is “error boundary”. In this article, we will see what is error boundary, and how to log errors from error boundary to Atatus.