Memoize stateful AppWrap components

[masenf]

Now that StateProvider and EventLoopProvider are defined as dynamic app_wrap components rather than static providers, it is necessary to auto-memoize (convert to individual react components) any component that depends on state, so that its hooks drop into the auto-memo component, rather than in the parent AppWrap component where the StateProvider has not yet provided the value being depended on.

This is also advantageous generally for preventing whole-page re-renders when an app_wrap component's dependent vars change, since the page component itself is ultimately a descendent of the AppWrap.

Fixes #6650

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing masenf/memoize-stateful-app-wrap (c0608f4) with main (6a91fbd)}

Footnotes

1. 8 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[greptile-apps]

Greptile Summary

This PR adds a memoization pass for stateful app_wrap components so their React hooks land inside their own memo modules rather than hoisting into the top-level AppWrap function — above the StateProvider where useContext cannot resolve.

• _memoize_stateful_app_wraps is inserted in compile_app immediately after App._app_root assembles the wrapper chain; it drives MemoizeStatefulPlugin against the assembled root and registers resulting memo definitions on the shared CompileContext, so the existing compile_memo_components pass emits them normally.
• ErrorBoundary (carrying an on_error event trigger) is the primary built-in wrap that gets extracted; tests are updated to match its memoized tag via regex rather than hardcoding the full inline JSX, and a new test_stateful_app_wrap_is_memoized end-to-end test verifies that useContext(StateContexts…) no longer appears in the AppWrap body while the memo module carries it instead.

Confidence Score: 5/5

The change is well-scoped: it inserts a single extra plugin pass over the already-assembled AppWrap chain and writes memo definitions into the existing compile context dict; all downstream emit logic is unchanged.

The new _memoize_stateful_app_wraps helper correctly passes the real compile_context so memo definitions reach compile_memo_components. The isolated CompilerHooks(plugins=(MemoizeStatefulPlugin(),)) for this pass is intentional — imports are collected afterwards via _get_all_imports() on the returned root. New and updated tests exercise both the structural output and the memo-module content.

No files require special attention.

Important Files Changed

Filename	Overview
reflex/compiler/compiler.py	Adds _memoize_stateful_app_wraps helper that runs the assembled AppWrap chain through MemoizeStatefulPlugin before emitting the app-root JS, correctly registering memo definitions on the shared compile_context.
tests/units/test_app.py	Updates existing tests to account for the memoized ErrorBoundary tag (replacing large inline JSX assertions), adds test_stateful_app_wrap_is_memoized covering the full compile path, and introduces _find_error_boundary_memo_tag helper for robust regex-based tag extraction.
news/6651.bugfix.md	Changelog entry for the bugfix.

_{Reviews (1): Last reviewed commit: "add news fragment" | Re-trigger Greptile}