wix-cli-extension-registration

Registers Wix CLI extensions in src/extensions.ts using app builder .use() chains.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/ESSSoWhat/live-translate-realtime-dubbing --skill wix-cli-extension-registration-esssowhat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-extension-registration
Source: https://github.com/ESSSoWhat/live-translate-realtime-dubbing/tree/main/wix-app/np/.agents/skills/wix-cli-extension-registration
Command: npx skills add https://github.com/ESSSoWhat/live-translate-realtime-dubbing --skill wix-cli-extension-registration-esssowhat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Newly created Wix CLI extensions do not appear in the dashboard, editor, or checkout flows until they are registered in the central src/extensions.ts file, and missing .use() calls are the most common cause of extensions silently failing. ## Core Features & Use Cases - Extension Registration: Import extension modules and chain them with .use() calls on the app builder in src/extensions.ts. - Scalable Patterns: Choose between a simple direct-import pattern for small apps and a programmatic re-export pattern for large apps. - Troubleshooting Guidance: Diagnose missing .use() calls, wrong import paths, export name mismatches, and incorrect builder methods. - Use Case: After generating a new dashboard page extension, add its import and .use(dashboardpageMyPage) call to src/extensions.ts so the page appears in the Wix dashboard sidebar. ## Quick Start Register my new Wix extension by adding its import and .use() call to src/extensions.ts.

Frequently Asked Questions about wix-cli-extension-registration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register a Wix CLI extension in extensions.ts?

Import the extension from its extensions.ts file and add a .use(extensionName) call to the app builder chain in src/extensions.ts. Multiple extensions are chained together with consecutive .use() calls on the same builder.

Why is my Wix extension not appearing in the dashboard?

The most common cause is a missing .use() call in src/extensions.ts, which is the single entry point the Wix CLI uses to discover extensions. Verify the import path matches the file location and the export name matches the import.

Which Wix extension types require registration in extensions.ts?

Dashboard pages, site widgets, embedded scripts, service plugins, and event handlers all require registration via .use() calls. Backend API endpoints built as Astro server endpoints are auto-discovered and do not need registration.

What naming convention do Wix extension exports follow?

Export names follow the pattern {extensiontype}{CamelCaseName}, where the type prefix is lowercase with no separators. Examples include dashboardpageCartPopupManager, embeddedscriptCouponPopup, and sitewidgetCountdownWidget.

How do I register many Wix extensions in a large app?

Re-export all extensions from a central src/index.ts, then import them as a namespace in src/extensions.ts and loop over Object.values() calling appBuilder.use() for each. This avoids manually maintaining a long chain of imports.