What is Flow (JS)?
Who uses Flow (JS)?
Why developers like Flow (JS)?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Flow (JS) in their tech stack.
I use TypeScript because the tooling is more mature (the decision to discontinue TSLint in favor of moving all its checks to ESLint is a thoughtful and mature decision), there's a ton of examples and tutorials for it, and it just generally seems to be where the industry is headed. Flow (JS) is a fine tool, but it just hasn't seen the uptake that TS has, and as a result is lacking a lot of the nicer small things, like thorough Visual Studio Code integration, offered by TS.
We use Relay because it's ability to generate Flow (JS) types based on given GraphQL fragments gives an immense amount of type safety. The relay-compiler helps us verify queries are valid before we build the app. Relay's ability to colocate queries with components, and compose many fragments, makes it easy to build a new component and get the data the component needs.
I think our #Frontend stack is pretty standard – but we have taken some deviations from a typical modern stack:
Yarn instead of npm. When yarn debuted, we never looked back. Now npm has pretty much caught up with speed and lockfiles, but yarn gives me confidence that my dependency installs are deterministic. Really interested in the plug-n-play (PnP) feature that removes the need for a node_modules folder, but haven't implemented this yet.
Flow (JS)'s Features
- Type Inference
- Easy Integration
- Realtime Feedback