Mention that local plugin server entry must be JavaScript without SDK - #3350
Merged
pwizla merged 1 commit intoJul 24, 2026
Merged
Conversation
…aScript without SDK
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pwizla
approved these changes
Jul 24, 2026
pwizla
left a comment
Collaborator
There was a problem hiding this comment.
Thank you, @singhvishalkr
The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
Setting a local plugin in a monorepo environment without the Plugin SDKsection listsstrapi-server.js|tsas the server entry point, which implies a TypeScript server entry works for this setup. It does not when the plugin is loaded directly without the SDK build or watch step.Strapi loads a local plugin's server entry point through the Node-side config loader (
packages/core/core/src/utils/load-config-file.ts), which only resolves.jsand.jsonfiles and returns an empty object for any other extension. The plugin loader defaults the server entry to./strapi-server.js, so astrapi-server.tsentry is not transpiled at load time and the plugin's server code silently does not load. The admin entry point can stay TypeScript because the admin panel build compiles it.I added a
:::cautionadmonition to the Server entry point subsection to document this current behavior, which matches what several people ran into in the linked issue.Related issue(s)/PR(s)
Relates to #3025