LegacyBridge — svelte Architecture
Maintains compatibility with Svelte 4 class-based component APIs.
Entity Profile
Dependency Diagram
graph TD subdomain_ClientRuntime_LegacyBridge["LegacyBridge"] 686ca949_4d11_24e5_89bf_2c8c02e51cde["class.js"] subdomain_ClientRuntime_LegacyBridge --> 686ca949_4d11_24e5_89bf_2c8c02e51cde e70d565a_b58f_b8a3_6358_70d749ddae50["legacy.js"] subdomain_ClientRuntime_LegacyBridge --> e70d565a_b58f_b8a3_6358_70d749ddae50 beb52c0c_aac9_0902_72a9_1450944244cf["svelte-component.js"] subdomain_ClientRuntime_LegacyBridge --> beb52c0c_aac9_0902_72a9_1450944244cf b0dea6fe_a39b_1574_4bd3_e0f24d88074a["misc.js"] subdomain_ClientRuntime_LegacyBridge --> b0dea6fe_a39b_1574_4bd3_e0f24d88074a f0137cbd_ade3_c5ec_547b_b722ffb28e2a["legacy.js"] subdomain_ClientRuntime_LegacyBridge --> f0137cbd_ade3_c5ec_547b_b722ffb28e2a 309b6da7_c79b_4906_049d_a61ee844e1d7["lifecycle.js"] subdomain_ClientRuntime_LegacyBridge --> 309b6da7_c79b_4906_049d_a61ee844e1d7 48cf26f8_bf34_fd7a_3d52_cc963051e167["context.js"] subdomain_ClientRuntime_LegacyBridge --> 48cf26f8_bf34_fd7a_3d52_cc963051e167 style subdomain_ClientRuntime_LegacyBridge fill:#6366f1,stroke:#818cf8,color:#fff
Relationship Graph
Domain
Functions
- add_legacy_event_listener()
- add_svelte_meta()
- bubble_event()
- capture_signals()
- check_target()
- component()
- component_api_changed()
- component_api_invalid_new()
- component_root()
- init()
- invalidate_inner_signals()
- legacy_api()
- legacy_recursive_reactive_block()
- legacy_rest_props()
- legacy_rest_props_handler.deleteProperty()
- legacy_rest_props_handler.get()
- legacy_rest_props_handler.getOwnPropertyDescriptor()
- legacy_rest_props_handler.has()
- legacy_rest_props_handler.ownKeys()
- legacy_rest_props_handler.set()
- lifecycle_legacy_only()
- observe_all()
- reactive_import()
- rune_outside_svelte()
- set_class()
- set_component_context()
- set_dev_current_component_function()
- svelte_boundary_reset_noop()
- svelte_boundary_reset_onerror()
- update_legacy_props()
- with_script()
Source Files
- packages/svelte/src/internal/client/dom/elements/class.js
- packages/svelte/src/internal/client/context.js
- packages/svelte/src/internal/client/dev/legacy.js
- packages/svelte/src/internal/client/legacy.js
- packages/svelte/src/internal/client/dom/legacy/lifecycle.js
- packages/svelte/src/internal/client/dom/legacy/misc.js
- packages/svelte/src/internal/client/dom/blocks/svelte-component.js
Source
- packages/svelte/src/internal/client/dom/elements/class.js
- packages/svelte/src/internal/client/context.js
- packages/svelte/src/internal/client/dev/legacy.js
- packages/svelte/src/internal/client/legacy.js
- packages/svelte/src/internal/client/dom/legacy/lifecycle.js
- packages/svelte/src/internal/client/dom/legacy/misc.js
- packages/svelte/src/internal/client/dom/blocks/svelte-component.js
Frequently Asked Questions
What is the LegacyBridge subdomain?
LegacyBridge is a subdomain in the svelte codebase, part of the ClientRuntime domain. Maintains compatibility with Svelte 4 class-based component APIs. It contains 7 source files.
Which domain does LegacyBridge belong to?
LegacyBridge belongs to the ClientRuntime domain.
What functions are in LegacyBridge?
The LegacyBridge subdomain contains 31 function(s): add_legacy_event_listener, add_svelte_meta, bubble_event, capture_signals, check_target, component, component_api_changed, component_api_invalid_new, and 23 more.
Analyze Your Own Codebase
Get architecture documentation, dependency graphs, and domain analysis for your codebase in minutes.
Try Supermodel Free