import/no-dynamic-require Restriction

What it does

Forbids imports that use an expression for the module argument. This includes dynamically resolved paths in require or import statements.

Why is this bad?

Using expressions that are resolved at runtime in import statements makes it difficult to determine where the module is being imported from. This can complicate code navigation and hinder static analysis tools, which rely on predictable module paths for linting, bundling, and other optimizations.

Examples

Examples of incorrect code for this rule:

require(name);
require(`../${name}`);

Examples of correct code for this rule:

require("../name");
require(`../name`);

Configuration

This rule accepts a configuration object with the following properties:

esmodule

type: boolean

default: false

When true, also check import() expressions for dynamic module specifiers.

How to use

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

CLI

oxlint --deny import/no-dynamic-require --import-plugin

Config (.oxlintrc.json)

{
  "plugins": ["import"],
  "rules": {
    "import/no-dynamic-require": "error"
  }
}

References

• Rule Source