Skip to main content

Plugins migration summary

🚧 Work in progress

This page is a work-in-progress and some links are currently missing.

The present page is intended to be used as a short summary of everything to consider if you are a plugin developer intending to migrate your plugin from Strapi v4 to Strapi 5. The page quickly describes the changes affecting plugins and links to additional resources where necessary.

Back-end changes​

  • The Entity Service API from Strapi v4 is deprecated and Strapi 5 uses the Document Service API instead. A migration guide is available to help you transition to the Document Service API.
  • General Strapi v4 to Strapi 5 breaking changes might apply.
  • You can use the new Plugin CLI to generate plugins and publish them on NPM and/or submit them to the Marketplace.

Front-end changes​

  • The Design System is upgraded to v2 in Strapi 5:
    • There are no big visual changes, except for icons.
      (the link will be added in the upcoming weeks)
    • A migration guide will be available.
      (the link will be added in the upcoming weeks)
    • A list of breaking changes specific to the Design System will be available in the Design System documentation.
      (the link will be added in the upcoming weeks)
    • General Strapi v4 to Strapi 5 breaking changes might apply.
  • The helper-plugin is deprecated. A migration reference is available to help you transition away from the helper-plugin.
  • Strapi does not alias dependencies any longer. The 4 dependencies that are expected to be used by all client facing code are declared at the project level (react/react-dom/styled-components & react-router-dom). If you do not declare your dependencies that you use e.g. axios there's a likelihood users could face unforeseen issues with your plugin.

Custom providers​

Custom providers for the Email and Upload plugins need conversion only if they were using the Entity Service API (please refer to the Entity Service API to Document Service API migration guide).