Flow vs TypeScript in 2026

This week’s JavaScript Weekly (#790) leads with a post by Meta’s George Zahariev comparing Flow and TypeScript as they stand in 2026, noting that Flow’s syntax has converged closely with TypeScript’s over the years. The issue also packs in significant releases and a standout deep-dive on how TanStack slashed type-checking overhead.

What’s actually new

The Flow vs TypeScript comparison highlights that Flow’s stricter defaults now reject several crash-prone patterns that TypeScript’s strict mode still accepts, and Flow has added its own features like exhaustive match expressions. For teams that haven’t looked at Flow in years, the convergence in syntax is worth noting — the differences are increasingly about strictness philosophy rather than language shape.

Beyond the headline piece, this issue carries real weight in its release notes. Playwright 1.61 adds passkey registration and testing plus a new WebStorage API for reading and writing localStorage and sessionStorage directly. ESLint v10.5.0 refines five core rules to highlight smaller code ranges, reducing the problem where a single squiggly line shadows other issues in your editor. TanStack AI enters beta as a framework- and provider-agnostic AI toolkit. And several major frameworks — SvelteKit 3.0, Vue 3.6, Vite 8.1, Astro 7.0 — are all in pre-release simultaneously, which is an unusual amount of ecosystem churn happening at once.

The TanStack Table v9 article is also worth your time if you author type-heavy libraries: it documents how the team used tsc diagnostics to cut type-checking work by 62–86% after modular generics introduced noticeable editor lag.

What it means for your config

The Flow piece doesn’t detail specific config changes, but if your project uses TypeScript’s strict mode and you’ve considered Flow, the implication is that Flow’s defaults are even stricter out of the box — meaning a migration would likely surface additional type errors rather than fewer.

For ESLint users on v10.x, the v10.5.0 change to narrower diagnostic ranges shouldn’t require config updates, but it may change how your editor surfaces warnings — worth upgrading to see if previously hidden issues become visible.

The simultaneous betas of SvelteKit 3.0, Vue 3.6, Vite 8.1, and Astro 7.0 are worth tracking if your build configs depend on any of them. The source doesn’t detail breaking changes for these, so hold off on upgrading production configs until stable releases land with migration guides.

Playwright 1.61’s new WebStorage API and passkey support may require updates to your test configuration if you want to take advantage of them, but the source doesn’t specify the exact config shape — check the Playwright docs directly.

Recommended next step

If you maintain a type-heavy library, the TanStack type-checking article is the most actionable item here — read it for concrete tsc diagnostic techniques you can apply today. For everyone else, this is a good week to audit which of those major framework betas (SvelteKit, Vue, Vite, Astro) are in your dependency tree and set up notifications for their stable releases so you’re not caught off guard by breaking config changes later.

---

Read the full announcement on JavaScript Weekly → Flow vs TypeScript in 2026