Update plugin Component examples to use non-deprecated import pattern

[jhoward1994]

What does it do?

Updates the plugin development docs so every addMenuLink / createSettingSection / addSettingsLink / addSettingsLinks example uses the non-deprecated, type-correct Component pattern:

Component: () => import('./pages/App'),

instead of the previously documented:

Component: async () => {
  const { App } = await import('./pages/App');
  return App;
},

The page module (e.g. admin/src/pages/App.tsx) must therefore export the component as default.

A short :::note block has been added under the menu-link example to call this requirement out for users migrating from the old pattern.

Why is it needed?

The current docs pattern is deprecated by @strapi/admin's own runtime and inconsistent with the typed signature the runtime ships:

I think the docs are showing a pattern that Strapi itself asks users to stop
using, and that doesn't typecheck against the API's published types.

Support for sdk-plugin work from strapi/sdk-plugin#107

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview, Comment	Apr 30, 2026 0:58am

[pwizla]

Perfect! Thank you, Jamie! 🚀

[jhoward1994]

Thanks both! @pwizla I think we can actually go ahead and merge this now. It's accurate today and doesn't need to wait on strapi/sdk-plugin#107 or any other PRs