prefer-modules-enum - ESLint plugin rules

This rule prefers Modules.* enum members over magic module-name strings in resolve(...) calls.

Severity#

warn. This rule is enabled in the recommended preset.

What it Targets#

This rule targets all files in your project. It reports calls to resolve(...) that pass a known module-name string, such as "product" or "sales_channel", instead of the matching Modules member.

The following code is reported by the rule:

src/api/example.ts
1// non-compliant2const productModule = req.scope.resolve("product")

Instead, use the Modules enum:

src/api/example.ts
1// compliant2import { Modules } from "@medusajs/framework/utils"3
4const productModule = req.scope.resolve(5  Modules.PRODUCT6)

Why it's Important#

The Modules enum gives you a single, type-safe source for module names. Using it avoids typos in magic strings and makes module dependencies easier to find and refactor.

Fixable#

This rule is auto-fixable. Run the linter with the --fix option to apply the fix automatically.

Turn it Off#

To turn off this rule, set it to off in your ESLint configuration:

eslint.config.ts
1import { defineConfig } from "eslint/config"2import medusa from "@medusajs/eslint-plugin"3
4export default defineConfig([5  ...medusa.configs.recommended,6  {7    rules: {8      "@medusajs/prefer-modules-enum": "off",9    },10  },11])

Or disable it for a single line using an inline comment:

Code
1// eslint-disable-next-line @medusajs/prefer-modules-enum2const productModule = req.scope.resolve("product")