Register plugin routes before the Medusa core routes

[thetutlage]

Load plugin routes before the Medusa core routes, since it will allow the plugin to define routes with higher priority than Medusa. Here are couple of examples.

• Plugin registers a route called "/products/active"
• Medusa registers a route called "/products/:id"

Now, if Medusa routes gets registered first, then the /products/active route will never be resolved, because it will be handled by the /products/:id route.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 22, 2024 9:38am

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			May 22, 2024 9:38am
docs-ui	⬜️ Ignored (Inspect)			May 22, 2024 9:38am
medusa-docs	⬜️ Ignored (Inspect)			May 22, 2024 9:38am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 32748fa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sradevski]

We need to revisit our entire routing TBH as it is a bit of a mess, but this works for now

[adrien2p]

LGTM, as discussed, a bigger work will have to be done for the route loading

[riqwan]

LGTM!