component-usage-analysis

To find all Twig includes of a specific Drupal component, you analyze component dependencies and usage patterns within the library. This identifies every location where the target component is referenced, ensuring safe refactoring and code audits.

Yes, you can check if a Drupal Twig component is safe to remove by performing an impact analysis. This process lists all consumers and mock references of the component, ensuring no critical functionality breaks during deletion.

Component dependency tracking in a Twig library is the process of identifying Twig includes and mock references to specific components. It helps developers understand usage patterns and analyze the impact of modifying shared components.

To track which Drupal components use a specific property, you perform property tracking within the component library. This identifies all components that use the target property, helping you analyze the impact of refactoring that specific attribute.

Yes, this component analysis tool works with mock references. It specifically identifies mock references to specific components alongside Twig includes, providing a comprehensive audit of how components are utilized across the library.