Flow

A lot of our open-source users are rightfully observing that the Flow team has effectively stopped paying attention to an ever-growing list of issues and PRs on GitHub.

We recently ported MemSQL Studio's 30 thousand lines of JavaScript from using Flow to TypeScript. In this article, I describe why we ported our codebase, how it took place and how it has been working out for us.

These are some of the sticking points that led me to give Flow a try, and although it’s still early, I’m liking what I see so far, and here’s why…

Why does it make sense to use FlowType or TypeScript when working with JavaScript?

It is time to rethink how Flow models React.

The Flow: Type Checking with Flow in React + Redux tutorial will teach you how to use Flow in a React JS + Redux environment.

JavaScript is a language of add-ons, and one of its more recent trends is typing. There are obvious benefits to typing, but what are the drawbacks? Should you choose Flow or TypeScript? Why use types at all? And why not just go straight to Reason? This session will provide some insight into these questions, peppered with examples from the real world.

Should you use Flow or TypeScript in your next React project? I recently had a bit of a dilemma with it for a new project and I would like to share my experience with it.

Learn how to test, debug, and optimize your React code with tools like Jest, Chrome, ESLint, and flow.