This guide explains how to add a dashboard page extension to your new Wix CLI project as part of migrating an app from the legacy Wix CLI.
| Legacy | New |
|---|---|
src/dashboard/pages/<name>/page.json | src/extensions/dashboard/pages/<name>/<name>.extension.ts |
src/dashboard/pages/<name>/page.tsx | src/extensions/dashboard/pages/<name>/<name>.tsx |
To move existing files into the new project:
src/extensions/dashboard/pages/<name>/.page.tsx from the legacy project's src/dashboard/pages/<name>/ folder into the new project's src/extensions/dashboard/pages/<name>/ folder, and rename it to <name>.tsx..tsx file if needed, including imports of backend code.Don't copy the old page.json file. It is replaced by a new .extension.ts file.
In src/extensions/dashboard/pages/<name>/, create <name>.extension.ts:
| Field | Source | Required |
|---|---|---|
id | id from page.json | Yes. Must match legacy value to preserve the extension. |
title | title from page.json | Yes |
routePath | Slugified version of the title, for example "About" → "about" | Yes |
component | Path to the .tsx file, relative to src/ | Yes |
Important:
The id must match the value from the legacy page.json. Otherwise, the new entry is treated as a separate extension instead of a continuation of the legacy one.
In the new project, in src/extensions.ts, import the extension and add it with .use():
Return to the Test, build, and release step in the main migration guide.
Last updated: 29 June 2026