Fix bundled library subpath serialization

[harsh21234i]

Summary

Fixes issue #6975.

compile_app() was clearing explicit bundle_library() registrations during frontend compilation. Dynamic components
also failed to rewrite bundled library subpath imports, such as Lucide deep imports.

Changes

• Preserve user-registered bundled libraries during compilation.
• Rewrite bundled default, named, and namespace subpath imports through window.__reflex.
• Add unit tests for bundled-library preservation and subpath serialization.
• Add browser integration coverage using a dynamically rendered Lucide icon.
• Add required bugfix news fragments.

Tests

• uv run pytest tests/units/compiler/test_dynamic_components_codegen.py tests/units/compiler/test_compiler.py -q
• uv run pytest tests/integration/test_dynamic_components.py -q
• Ruff checks and formatting pass.
• Pyright passes for the changed source modules.

[greptile-apps]

Greptile Summary

The PR preserves explicit bundled-library registrations across compilation and routes dynamic subpath imports through their corresponding window.__reflex module namespaces.

• Separates explicit library registrations from compile-derived registrations.
• Generates unique browser namespace aliases for normalized library-name collisions.
• Adds unit and browser integration coverage for Lucide subpath imports.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/reflex-base/src/reflex_base/components/dynamic.py	Tracks explicit registrations separately and reconstructs bundled subpath imports from exact window namespace entries.
packages/reflex-base/src/reflex_base/registry.py	Adds registration-context storage and copying for explicitly bundled libraries.
reflex/compiler/compiler.py	Preserves explicit registrations during compile resets and generates collision-free window-library aliases.
packages/reflex-components-radix/src/reflex_components_radix/plugin.py	Registers Radix Themes as a compile-derived dependency while retaining compatibility with older reflex-base versions.
tests/units/compiler/test_dynamic_components_codegen.py	Covers exact-subpath default and named import reconstruction plus app-root bundling.
tests/units/compiler/test_compiler.py	Covers explicit-registration preservation, stale derived-registration removal, and normalized alias collisions.
tests/integration/test_dynamic_components.py	Exercises a dynamically rendered Lucide icon through the browser integration path.

_{Reviews (4): Last reviewed commit: "Document bundled library helper return v..." | Re-trigger Greptile}

[codspeed-hq]

Merging this PR will not alter performance

✅ 32 untouched benchmarks
⏩ 8 skipped benchmarks¹

---

_{Comparing harsh21234i:fix/6975-bundled-library-subpaths (f8b7f63) with main (9a26753)}

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. ↩

[cubic-dev-ai]

All reported issues were addressed across 7 files

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

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 8 files (changes from recent commits).

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

Re-trigger cubic</sub>

[masenf]

can you explain what scenarios result in triggering this bug? i understand what's going on, but it seems like most situations that matter, like hot-reload would end up re-bundling the needed libraries anyway.

[harsh21234i]

I agree that normal hot-reload may re-run the app module and re-register the library, which can mask the problem. The bug is not limited to source-file hot-reload, though.

The failure occurs when bundle_library() is called during app/component registration and compile_app() later resets the bundled-library list before compilation.
This can happen even on the first compile, or on a later compile where the existing app and RegistrationContext are reused without re-executing the registration code.

Examples include repeated compilation in the same process, cached app modules, compiler/AppHarness tests, export/build paths, and dynamic component serialization. In those cases, the explicit library registration is lost even though the app/context is still valid. Hot- reload may re-register it, but the compiler should not depend on hot- reload re-executing user code to preserve an explicit registration.