ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
React Navigation keeps screens mounted after you navigate away, so useEffect fires only once. useFocusEffect scopes side effects to focus events—if you memoize the callback and clean up properly.
React Navigation keeps screens mounted after you leave them, so a plain useEffect with an empty dependency array never fires again. useFocusEffect runs side effects on every focus, but only if you wrap the callback in useCallback.
Rollup’s sideEffects flag lets you prune unused code, but it must be used carefully. Learn how to set the flag, test bundle size gains, and avoid breaking your app.
A diagnostic guide to help you decide between MobX reaction and autorun for React side‑effects, with checks, fixes, and escalation steps.
A decision guide for picking MobX side‑effect primitives (autorun, reaction, when) and batching mutations with runInAction in React, including a comparison table, trade‑offs, and a concrete component example.
Elm side-effects: use Cmd for simple one-shot effects and Task for composable, error-handling operations. A decision guide with a concrete HTTP example.
The goal is to keep the number of JavaScript requests the browser makes during development low while avoiding an overly large pre‑bundled chunk that hurts initial load time. Vite achieves this by pre‑bundling dependencies with esbuild, but the decision of which packages to bundle depends on Vite’s heuristic for detecting side‑effects. This heuristic is docum
Rollup builds a static module graph from ES module import and export declarations and uses that graph for tree-shaking and code splitting. The goal is to clarify the documented decision rules for which exports are considered unused and removed, and which modules are emitted into separate chunks for lazy loading. Constraints include purely static analysis wit
Mocha’s global `--retries` flag reruns the entire test suite after a failure, which repeats all `before` hooks for each retry. If a test performs non‑idempotent writes such as inserting records, the side effects can be duplicated across retries. The documentation states that retries execute after the failing test’s `after` hooks, but it does not specify whet
reactnavigation
rollup
mobx
react
vite