You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building a MedusaJS plugin with dynamic route segments (e.g., admin/custom/[id]/page.tsx), the [id] folder is renamed to _id_ in the build output. This breaks the dynamic routing functionality in the admin UI.
Expected behavior
The [id] folder should be preserved in the build output, allowing dynamic routes to work as expected.
Actual behavior
The [id] folder is renamed to _id_ in the build output, causing dynamic routes to fail.
Hi @MounsifChr, thanks for the report. We are aware of the issue, admin extensions in plugin currently don't work for production. It will be fixed in 2.6.2/2.7.0 which should be released next week.
In the meantime, if you want to carry on with working on your plugin you can use the snapshot versions that you can find on this PR: #11720.
Package.json file
Node.js version
v22.0.0
Database and its version
PostgreSQL 14.15
Operating system name and version
Ubuntu 22.04.5 LTS
Browser name
Firefox
What happended?
When building a MedusaJS plugin with dynamic route segments (e.g.,
admin/custom/[id]/page.tsx
), the[id] folder
is renamed to_id_
in the build output. This breaks the dynamic routing functionality in the admin UI.Expected behavior
The
[id] folder
should be preserved in the build output, allowing dynamic routes to work as expected.Actual behavior
The
[id] folder
is renamed to_id_
in the build output, causing dynamic routes to fail.Link to reproduction repo
https://github.com/MounsifChr/medusajs-plugin-route-segments-issue/tree/master/medusa-plugin-wishlist
The text was updated successfully, but these errors were encountered: