Skip to content

Plugin migration updates#2208

Merged
pwizla merged 7 commits intonextfrom
v5/plugin-migration-updates
Sep 12, 2024
Merged

Plugin migration updates#2208
pwizla merged 7 commits intonextfrom
v5/plugin-migration-updates

Conversation

@maccomaccomaccomacco
Copy link
Contributor

What does it do?

This PR brings updates to the plugin migration documentation.

Why is it needed?

I have mostly included information to suggest the migration to the Plugin SDK. Even if plugin development is doable in many different ways, I think we should recommend the adoption of the Plugin SDK. And so, also the migration should be focused mainly on the plugin SDK.

@vercel
Copy link

vercel bot commented Sep 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 12, 2024 0:19am

@strapi-cla
Copy link

strapi-cla commented Sep 12, 2024

CLA assistant check
All committers have signed the CLA.

@maccomaccomaccomacco maccomaccomaccomacco added pr: updated content PRs updating existing documentation content source: Dev Docs PRs/issues targeting the Developer Docs labels Sep 12, 2024
## Back-end changes
Alternatively, you can manually update your Strapi v4 plugin to use the Plugin SDK.
The manual steps include:
1. If your code uses a format other than CommonJS, update the `package.json` file and specify the appropriate exports property.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure it's enough to say this way
@alexandrebodin wdyt?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can go ahead with this I'll update it in my PR 👍

@maccomaccomaccomacco
Copy link
Contributor Author

I probably missed adding that if you're developing with the plugin SDK, the code needs to be transitioned to ESM.
But I'm not sure it's still valid, I know that Alex was working on this.
@alexandrebodin FYI, when you'll bring your updates

@alexandrebodin
Copy link
Member

I'll do my updates on top of this PR

Copy link
Collaborator

@pwizla pwizla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great suggestions, Marco, thank you!

I'll commit my suggestions, then merge the PR, so that Alex can improve things in his own PR if he wishes to.

@pwizla pwizla merged commit 564f65c into next Sep 12, 2024
@pwizla pwizla deleted the v5/plugin-migration-updates branch September 12, 2024 12:11
@pwizla pwizla added this to the 5.0.0 (stable) milestone Sep 12, 2024
@pwizla pwizla self-assigned this Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: updated content PRs updating existing documentation content source: Dev Docs PRs/issues targeting the Developer Docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants