Usages tab — “Who uses this component?”

Usages tab — “Who uses this component?”

A new Usages tab in the component editor answers the question every developer eventually asks: “which other components use this one?”

Click the tab and it scans all open workspace projects for templates that reference the current component as an element — both inline `` tags in HTML and : ComponentName { declarations in WOD files. Results appear in a two-column table showing the using component’s name and its project. Double-click any row to jump straight to that component’s template.

The scan runs in the background on first tab activation, so it never blocks your editing. Hit Refresh to re-scan after making changes. Works for both standalone and bundle templates, and catches cross-project references.

Extract Wrapper

A new refactoring that is the inverse of Extract Component. Select the content that should stay in the current component, press Cmd+2, X (or Edit > Refactor > Extract Wrapper…), and enter a name. Everything around the selection — the surrounding page chrome — is extracted into a new wrapper component with `` where the selection was. The original template becomes just the selection wrapped in the new component tag.

Typical use case: extracting a page layout (navigation, header, footer) into a reusable wrapper, leaving only the page-specific content in the original component.

Extract Component and Extract Wrapper: standalone template support

Both Extract Component (Cmd+2, E) and Extract Wrapper (Cmd+2, X) now correctly handle ng-objects projects — creating standalone .html template files instead of .wo bundles, and placing them in the correct resource folder.

From the changelog, March 7, 2026.