[benedikt-bartscher]

Stacked on #6100 — the diff includes its commits until that merges. The changes specific to this PR are in fb6992b and the merges of explicit-event-id-minification that follow it.

What this adds

Var name minification. REFLEX_MINIFY_VARS=1 shortens state var keys on the wire using a new optional vars section in minify.json (still schema version 1; older files load with no vars). A minified key is just its id, so a delta goes from {"a.b": {"items_rx_state_": []}} to {"a.b": {"c": []}}. reflex minify init/sync/validate/list/lookup cover vars, and the scheme digest includes them. Var ids that every JS object already has (constructor, __proto__, …) or that end in _rx_state_ are rejected.

A name resolver can be installed after states exist. RegistrationContext.set_name_resolver rebuilds the Vars every registered state holds. Backend dependency tracking and VarData.field_dependencies now key on classes and the resolver-independent default name, so they never go stale. This lets in-process AppHarness tests run fully minified. A Var built from state Vars before the install (e.g. a module-level component imported before minify.json was loaded) is not fixed; compiling fails with a message naming each stale reference instead of shipping a broken frontend.

One place builds wire keys. format_var_key / format_state_var (which reads through the prefixed local format_state_local from #6100) replace the ad-hoc name + FIELD_MARKER concatenations; update_vars_internal maps keys back through a per-state lookup, and state.js reads the hydrated flag's key from the compiled context instead of hardcoding it.

Notes

• setvar still sends the Python var name: it dispatches through the class hierarchy, where a per-state id would be ambiguous.
• REFLEX_PERF_MODE's check for stringified vars keys on the field marker, so it doesn't see minified vars.
• Router fields and is_hydrated are minified too; nothing in the frontend reads them by name anymore.
• New public API: NameResolver.resolve_var_name, reflex_base.utils.format.format_var_key / format_state_var.

Testing

• Unit tests for var ids, config validation, sync/prune, the stale-name check, rebuilding Vars on a late install, dependency tracking and always-dirty substates under renamed states, client-storage compile, update_vars_internal with minified keys, and the CLI.
• tests/integration/test_minification.py now runs in-process with framework states and vars minified.
• A downstream app driven by Playwright in prod with all three modes on: inherited, computed and backend vars, background tasks, ComponentState, cookie/localStorage persistence across tabs, dynamic routes; websocket frames carry no var or state names.

🤖 Generated with Claude Code

[greptile-apps]

Old events survive compilation

Events built under an earlier minified scheme can pass raise_for_stale_names unchanged. A module-level LiteralEventVar can store a.b.c; after the handler's ID changes to d, the default-name scan cannot match a.b.c, and the state-local scan does not inspect event strings. Compilation succeeds with an event the backend no longer registers—or now assigns to another handler.

The bundle carries the current scheme digest, so the handshake does not catch this. Track resolved event names when they are built, or rebuild these event Vars when installing the resolver.

[cubic-dev-ai]

2 issues found across 5 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/reflex-base/src/reflex_base/registry.py">

<violation number="1" location="packages/reflex-base/src/reflex_base/registry.py:76">
P2: This drops empty resolver segments, so registry keys diverge from the event names emitted by `format_event_handler` for a valid custom resolver. Preserve the formatter’s `handler.state is None` branch to keep inbound event dispatch consistent.</violation>
</file>

<file name="reflex/minify.py">

<violation number="1" location="reflex/minify.py:766">
P2: This live-name check can accept an event for a handler removed by a state reload because it consults the old issuer's resolver mapping without checking the current event registry. Verify that each issuer still has the recorded handler registered before returning it as live; otherwise compilation can emit an event the backend no longer handles.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: This drops empty resolver segments, so registry keys diverge from the event names emitted by format_event_handler for a valid custom resolver. Preserve the formatter’s handler.state is None branch to keep inbound event dispatch consistent.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At packages/reflex-base/src/reflex_base/registry.py, line 76:

<comment>This drops empty resolver segments, so registry keys diverge from the event names emitted by `format_event_handler` for a valid custom resolver. Preserve the formatter’s `handler.state is None` branch to keep inbound event dispatch consistent.</comment>

<file context>
@@ -59,6 +59,23 @@ def _rekey(
+    """
+    from reflex_base.utils.format import get_event_handler_parts
+
+    return ".".join(filter(None, get_event_handler_parts(handler)))
+
+
</file context>

Suggested change

	return ".".join(filter(None, get_event_handler_parts(handler)))
	state, name = get_event_handler_parts(handler)
	return name if handler.state is None else f"{state}.{name}"

[cubic-dev-ai]

P2: This live-name check can accept an event for a handler removed by a state reload because it consults the old issuer's resolver mapping without checking the current event registry. Verify that each issuer still has the recorded handler registered before returning it as live; otherwise compilation can emit an event the backend no longer handles.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At reflex/minify.py, line 766:

<comment>This live-name check can accept an event for a handler removed by a state reload because it consults the old issuer's resolver mapping without checking the current event registry. Verify that each issuer still has the recorded handler registered before returning it as live; otherwise compilation can emit an event the backend no longer handles.</comment>

<file context>
@@ -735,17 +735,53 @@ def _renamed_default_references() -> dict[str, str]:
+    for state_cls, handlers in issuers.items():
+        state_name = state_cls.get_full_name()
+        for handler in handlers:
+            if f"{state_name}.{ctx.get_handler_name(state_cls, handler)}" == name:
+                return None
+            labels.append(f"event handler {get_state_full_path(state_cls)}.{handler}")
</file context>