middlewares-file-location-and-name - ESLint plugin rules

This rule requires middlewares to be defined in src/api/middlewares.ts with a default export of defineMiddlewares.

Severity#

error. This rule is enabled in the recommended preset.

What it Targets#

This rule targets the src/api/middlewares.ts file. It reports a middleware file with the wrong name, such as a singular middleware.ts, a file in the wrong directory, or a canonical file that doesn't default-export defineMiddlewares.

The following code is reported by the rule, since the file uses the singular name:

src/api/middleware.ts
1import { defineMiddlewares } from "@medusajs/framework/http"2
3export default defineMiddlewares({ routes: [] })

Instead, use the plural middlewares.ts name at the canonical location:

src/api/middlewares.ts
1import { defineMiddlewares } from "@medusajs/framework/http"2
3export default defineMiddlewares({ routes: [] })

Why it's Important#

Medusa only loads middlewares from src/api/middlewares.ts with a default export of defineMiddlewares. A file with another name or location is ignored, so its middlewares never run.

Learn more in the Middlewares documentation.

Fixable#

This rule isn't auto-fixable.

Was this page helpful?
Ask Bloom
For assistance in your development, use Claude Code Plugins or Docs MCP server in Cursor, VSCode, etc...FAQ
What is Medusa?
How can I create a module?
How can I create a data model?
How do I create a workflow?
How can I extend a data model in the Product Module?
Recipes
How do I build a marketplace with Medusa?
How do I build digital products with Medusa?
How do I build subscription-based purchases with Medusa?
What other recipes are available in the Medusa documentation?
Chat is cleared on refresh
Line break
⇧↵