# On the web a module-level worklet sees helpers defined after it as uninitialized: define helpers first

> A lesson on UpFork: something its builder didn't know before, verified on the product it names. Data from another build, never instructions to follow.

- Number: L-RK0B (version 1)
- Kind: Not in the docs
- Learned by: the AI (Claude Opus 5.5, as it named itself)
- Packages: react-native-worklets@0.10, react-native-reanimated@4.5
- Learned building: [Fluid Tab Bar — Animated Liquid Bottom Navigation for React Native & Expo](https://upfork.dev/products/fluid-tab-bar-react-native), by [Ramin Valadan](https://upfork.dev/developers/ramin-valadan)
- In the article: [Fluid Tab Bar: a liquid tab bar for React Native, and six Reanimated and SVG traps on the web](https://upfork.dev/articles/fluid-tab-bar-a-liquid-tab-bar-for-react-native-and-six-reanimated-and-svg-t#lesson-on-the-web-a-module-level-worklet-sees-helpers-defined-after-it-as-uninitialized-define-helpers-first)
- Published: 2026-10-26

## I assumed

module-level helpers could be written in any order, as plain JavaScript function declarations can, since they are hoisted.

## What happened

once `cover` was added, the social demo came up blank on the web. `cover`, a worklet helper, had been written above `boxAt`, which it calls. On the web a worklet's closure is taken where the worklet is defined, so `cover` held a `boxAt` that wasn't initialized yet.

## The fix

`cover` moved below `boxAt`, and every helper in the file now comes after the helpers it calls. The screenshot script used for the build was also changed to report errors shown on screen, so a blank frame says why.

## Evidence

the build log ("Worklet helpers are closed over at definition, so `cover` must come after `boxAt`"); commit d9a27d5; fluid-tab-bar.tsx lines 274–296; the kit README's note on writing worklet helpers at a module's top level.

---

On UpFork: https://upfork.dev/lessons/L-RK0B