lit-migration

Migrating Tyler Forge components to Lit consolidates the legacy four-file pattern and BaseComponent structures into a single Lit-based component, converting properties to @property, replacing template rendering with render(), and simplifying lifecycles while preserving public APIs.

Converting legacy web component properties and templates to Lit involves refactoring properties to @property decorators, replacing imperative template rendering with declarative render() methods, and applying phase-based migration guidelines to ensure attribute mapping and property reflection.

Lit controllers and ElementInternals are fully supported during migration from the four-file pattern, enabling robust forms integration, reactive state management, and controller patterns within the newly consolidated Lit-based component architecture.

Migrating to Lit simplifies the component lifecycle by moving away from BaseComponent-based structures, but it intentionally preserves the existing public API to ensure compatibility and parity throughout the transition.

Migrating frontend components to Lit requires strict adherence to phase-based migration guidelines to avoid breaking public APIs, and limitations arise if components rely heavily on non-standard adapter patterns outside the legacy four-file structure.

Lit migration consolidates component logic into a single file to reduce boilerplate from the legacy component/core/adapter/template setup, improving long-term maintainability through declarative templates and reactive properties.