reflex-dev/reflex - CodSpeed

reflex

Blog Docs Changelog

Performance History

Latest Results

Merge remote-tracking branch 'upstream/main' into farhan/eng-11433-move-reflex-deploy-command-out-of-the-reflex-package-into # Conflicts: # reflex/reflex.py

FarhanAliRaza:farhan/eng-11433-move-reflex-deploy-command-out-of-the-reflex-package-into

34 minutes ago

benedikt-bartscher:shared-state-redis-fix

10 hours ago

Create separate context providing components for each state Instead of combining all states and dispatchers into the same component (which is the re-render domain), separate each state into its own provider component and combine those into StateProvider. Since StateProvider doesn't directly depend on each state's context, it doesn't have to re-render just because some substate changed. - `StateProvider` keeps its exported name -- it is the app-wrap tag in `reflex_base.components.state_context` -- and is now a pure composer; the per-substate reducer lives in a new `SubstateProvider`. - `DispatchProvider` publishes the plain registry object (`ref.current`) rather than the ref wrapper, so reads and writes agree. - Dispatcher registration runs in a layout effect. `EventLoopProvider` mounts below the state providers, so its passive effect connects the socket before any ancestor passive effect would have registered a dispatcher, and `state.js` treats a delta for an unregistered substate as a fatal state mismatch. Falls back to `useEffect` on the server, where `useLayoutEffect` warns. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015aV7hXqYysQQCFAu7dKxNX

masenf/memoize-state-provider-separately

10 hours ago

Add regression tests for context provider memoization Cover the ThemeProvider context-value memoization, the stable color-mode setters, the mount-only matchMedia listener, and the EventLoopProvider provider-element memo (including that the module-level dispatchers are still published outside the memo). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LPtTWGeWxL3p3ZH39TizSP

masenf/avoid-theme-rerenders

10 hours ago

Drop superseded error-boundary memo; add provider memoization regression tests main's `_memoize_stateful_app_wraps` already extracts the default ErrorBoundary app wrap into its own memo module, so the manual `memo()` in `default_error_boundary` is redundant and renamed the generated tag, breaking `test_app_wrap_compile_theme`. Add regression tests covering the ThemeProvider and EventLoopProvider memoization, plus a news fragment.

masenf/avoid-theme-rerenders

11 hours ago

Merge branch 'main' into masenf/memoize-state-provider-separately templates.py moved to packages/reflex-base since this branch forked, and the state/event-loop providers are now mounted as Var-driven app wraps instead of being hard-coded into the app root Layout. Re-apply the per-substate provider split on top of that layout: - `StateProvider` keeps its exported name (it is the app-wrap tag in `reflex_base.components.state_context`) and is now a pure composer; the per-substate reducer lives in a new `SubstateProvider`. - `DispatchProvider` publishes the plain registry object (`ref.current`) rather than the ref wrapper, so reads and writes agree. - Dispatcher registration runs in a layout effect. `EventLoopProvider` mounts below the state providers, so its passive effect connects the socket before any ancestor passive effect would have registered a dispatcher, and `state.js` treats a delta for an unregistered substate as a fatal state mismatch. Falls back to `useEffect` on the server, where `useLayoutEffect` warns.

masenf/memoize-state-provider-separately

11 hours ago

fix(compiler): release naming caches from the compile lifecycle `clear_hash_caches()` was called from `App.__call__`, which only the ASGI path reaches. `reflex export` and `reflex compile` get to a compile through `prerequisites.get_compiled_app` -> `App._compile` and never touch `__call__`, so those paths never released anything. Move the call into `App._compile` -- the single funnel every compile goes through -- inside a `finally`, so a failed compile does not leave the caches behind either. Covered by a test that fails under the old placement, on both the success and the exception path. Also add the root `news/` fragment: this PR now touches `reflex/`, so the changelog check requires one for the main package too. Corrects the reflex-base performance fragment, which claimed digests were unchanged -- true of the encoder rewrite alone, but later commits deliberately folded the defining module and dynamic imports into the hash, so generated memo module names do change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X8v1xEMwog6ZhP7hZYibFr

claude/optimize-deterministic-hash-u1dl2j

11 hours ago

docs(memoize): add changelog fragments and tighten the re-render claim Add news fragments for the reflex and reflex-base packages, and correct the docs paragraph: the page function no longer re-runs, but a sibling reading the same state still re-renders inside its own generated wrapper. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FNfPvVUGGMUQHh63V4Phbe

claude/auto-memoize-stateful-props-dqga0l

11 hours ago

Latest Branches

0%

ENG-11433 Move `reflex deploy` out of the framework into the Cloud CLI#6924

50 minutes ago

a74cb42

FarhanAliRaza:farhan/eng-11433-move-reflex-deploy-command-out-of-the-reflex-package-into

0%

fix: deliver linked state updates to all clients#6934

10 hours ago

a4cb90c

benedikt-bartscher:shared-state-redis-fix

0%

Create separate context providing components for each state#6181

10 hours ago

7473030

masenf/memoize-state-provider-separately

© 2026 CodSpeed Technology

Home Terms Privacy Docs