/wix-app

Extension Registration

src/extensions.ts is the single entry point that tells the build system which extensions exist. Without a .use() call for an extension, it does not load. HTTP endpoints are file-based routes and do not use this registration mechanism.

Registration is automatic via the CLI

For every CLI-supported extension type, wix generate --params updates src/extensions.ts for you — you do NOT need to write the import or the .use() call by hand. Verify the file was updated after each wix generate invocation. The one exception is HTTP_ENDPOINT: it is file-based, wix generate does not touch src/extensions.ts for it, and an unchanged file after generating an endpoint is expected (see below).

HTTP endpoints: no registration

wix generate --params '{"extensionType":"HTTP_ENDPOINT","name":"hello"}' creates the endpoint file without changing src/extensions.ts:

Leave app() unchanged. Do not add endpoint imports, .use() calls, or IDs. See BACKEND_API.md for supported versions and frontend URLs.

Manual recovery (when the CLI output drifts)

Edit src/extensions.ts directly only when:

• The CLI failed mid-run and left the file out of sync
• A user hand-edited the file and broke the chain

Each extension file is a default export from <folder>/<folder>.extension.ts. In src/extensions.ts, import it as a default import using the camelCase of the folder name, then chain .use(...):

import { app } from '@wix/astro/builders';
import myPage from './extensions/dashboard/pages/my-page/my-page.extension.ts';
import contactCreated from './extensions/backend/events/contact-created/contact-created.extension.ts';

export default app()
  .use(myPage)
  .use(contactCreated);

Re-run wix generate --params whenever possible — manual edits drift faster than CLI-generated ones.

Troubleshooting