← Back to rules

vitest/no-mocks-import Style

What it does

This rule reports imports from a path containing a __mocks__ component.

Why is this bad?

Manually importing mocks from a __mocks__ directory can lead to unexpected behavior and breaks Jest's automatic mocking system. Jest is designed to automatically resolve and use mocks from __mocks__ directories when jest.mock() is called. Directly importing from these directories bypasses Jest's module resolution system and can cause inconsistencies between test and production environments.

Examples

Examples of incorrect code for this rule:

import thing from "./__mocks__/index";
require("./__mocks__/index");

Examples of correct code for this rule:

import thing from "thing";
require("thing");

How to use

To enable this rule using the config file or in the CLI, you can use:

Config (.oxlintrc.json)

{
  "plugins": ["vitest"],
  "rules": {
    "vitest/no-mocks-import": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["vitest"],
  rules: {
    "vitest/no-mocks-import": "error",
  },
});

CLI

oxlint --deny vitest/no-mocks-import --vitest-plugin

Version

This rule was added in v0.0.13.

References

• Rule Source
• Upstream rule docs
• Open rule in Oxc Playground