wix-cli-extension-registration

Registers Wix CLI extensions with the app builder in src/extensions.ts.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/thisisjaymehta/login-with-email-test --skill wix-cli-extension-registration-thisisjaymehta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wix-cli-extension-registration
Source: https://github.com/thisisjaymehta/login-with-email-test/tree/main/.agents/skills/wix-cli-extension-registration
Command: npx skills add https://github.com/thisisjaymehta/login-with-email-test --skill wix-cli-extension-registration-thisisjaymehta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @wix/astro.

What problem does it solve? Newly created Wix CLI extensions do not appear or function until they are registered in the central src/extensions.ts file, and a missing .use() call is the most common cause of extensions silently failing. ## Core Features & Use Cases - Extension Registration: Import extension builders and chain them with .use() calls in src/extensions.ts so dashboard pages, site widgets, service plugins, event handlers, and embedded scripts are discovered by the build system. - Simple and Advanced Patterns: Choose between direct import-and-chain registration for small apps or programmatic registration via a re-export index for large apps. - Naming and Troubleshooting Guidance: Apply the {extensiontype}{CamelCaseName} export naming convention and diagnose issues like missing .use() calls, wrong import paths, and export name mismatches. - 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 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() chain in src/extensions.ts. Chain multiple extensions together with consecutive .use() calls.

Why is my Wix extension not appearing in the dashboard?

The most common cause is a missing .use() call in src/extensions.ts, since the Wix CLI discovers extensions only through that entry file. Add the import and .use() call, then rebuild the app.

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 need no registration.

What naming convention do Wix extension exports follow?

Export names follow the pattern {extensiontype}{CamelCaseName}, such as dashboardpageCartPopupManager or embeddedscriptCouponPopup. The type prefix is the extension type in lowercase with no separators.

Why does my Wix build fail with cannot find module after registering an extension?

The import path in src/extensions.ts does not match the extension file's actual location relative to src/. Verify the path points to the extension's extensions.ts file and that the exported name matches the import.