This guide explains how to add a dashboard menu plugin extension to your new Wix CLI project as part of migrating an app from the legacy Wix CLI.
| Legacy | New |
|---|---|
src/dashboard/menu-plugins/<name>/plugin.json | src/extensions/dashboard/menu-plugins/<name>/<name>.extension.ts |
Dashboard menu plugins are configuration-only. There is no component file.
In the new project:
src/extensions/dashboard/menu-plugins/<name>/.<name>.extension.ts:| Field | Source | Required |
|---|---|---|
id | id from plugin.json | Yes. Must match legacy value to preserve the extension. |
title | title from plugin.json | Yes |
extends | extends from plugin.json, the parent page this plugin extends | Yes |
iconKey | iconKey from plugin.json | Yes. Use '' if not set in legacy config. |
action | action object from plugin.json | Yes. Use { navigateToPage: { pageId: '' } } if not set in legacy config. |
subtitle | subtitle from plugin.json | No |
Important:
The id must match the value from the legacy plugin.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