Frontfriend installs component source in your repository. Your application can inspect and modify that source. Token generation and config-driven classes still depend on Frontfriend until those connections are explicitly removed.
Source ownership and independence
Owning component files is different from having zero Frontfriend dependencies. A component can import ffdc, config, utilities, icons and generated theme assets. Account for these dependencies when planning an exit.
Eject your system
Eject inlines tokens and component styling into the application’s Tailwind codebase. Use the tooling for your release and target, and inspect the generated changes before removing Frontfriend dependencies.
Plan a safe exit
Keep a complete repository baseline, exact dependency versions and an authorized snapshot of the Design System your application consumes. Run eject only with tooling verified for that release and target. Review generated source and styles, then run application typechecks, tests and production builds.
Verify offline builds where that is an exit requirement. Check light/dark themes, focus states and custom components, not only the first rendered page.
Coordinate production changes
The plan model assigns eject as a Self-serve capability and defines a managed operating workflow for Managed customers. Contact the team for the available path and review the terms.