Skip to content
← Back to rules

vitest/no-importing-vitest-globals Style

🛠️ An auto-fix is available for this rule.

What it does

The rule disallows importing any vitest global functions.

Why is this bad?

If a project is configured to provide Vitest functions as globals, this rule can be used to ensure that the globals are never imported via import or require.

Note that this rule should not be used if the globals config option is set to false in Vitest (false is the default configuration).

Examples

Examples of incorrect code for this rule:

js
import { test, expect } from "vitest";

test("foo", () => {
  expect(1).toBe(1);
});
js
const { test, expect } = require("vitest");

test("foo", () => {
  expect(1).toBe(1);
});

Examples of correct code for this rule:

js
test("foo", () => {
  expect(1).toBe(1);
});

How to use

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

json
{
  "plugins": ["vitest"],
  "rules": {
    "vitest/no-importing-vitest-globals": "error"
  }
}
ts
import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["vitest"],
  rules: {
    "vitest/no-importing-vitest-globals": "error",
  },
});
bash
oxlint --deny vitest/no-importing-vitest-globals --vitest-plugin

Version

This rule was added in v1.49.0.

References