// the take
A small React component (`<For>`) that replaces `.map()` with JSX-based for-of/for-in loops, complete with `ifEmpty` fallback and iteration metadata (index, isFirst, isLast). It's presented as part of a tongue-in-cheek "React Velcro Architecture" announced on April 1st, 2019 — the author is explicit that this is a parody of Angular/Vue-style directives, not a serious pitch to replace `.map()` in production code.
The implementation itself is solid for what it does: automatic key assignment via iteration metadata, support for Arrays, Map, Set, and Immutable.js iterables through a single `of` prop, and a separate `in` prop for plain objects. It ships both TypeScript (`.d.ts`) and Flow type definitions, and has actual test coverage with CI and Coveralls badges rather than being a toy with no verification.
No commits since April 2019 and no releases past that — this predates React 16.8's stabilization of hooks and has never been touched for React 18/19 concurrent rendering or JSX transform changes, so compatibility with modern React is unverified. It's a single-file library (`react-loops.js`) with no real architecture to speak of, and the author's own README calls the broader "Velcro" framing a joke, which makes it hard to tell how seriously to take the `<For>` component on its own merits. Using a render-prop component for list rendering also pulls in an extra layer of indirection and a dependency for something `array.map()` already does natively, with no performance or DX win documented anywhere in the README.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →