← Back to rules

unicorn/prefer-module Restriction

🚧 An auto-fix is planned for this rule, but not implemented at this time.

What it does

Prefer JavaScript modules (ESM) over CommonJS.

Why is this bad?

CommonJS globals and patterns (require, module, exports, __filename, __dirname) make code harder to migrate and can block ESM-only features.

Examples

Examples of incorrect code for this rule:

"use strict";
const foo = require("foo");
module.exports = foo;

Examples of correct code for this rule:

import foo from "foo";
export default foo;

How to use

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

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/prefer-module": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

export default defineConfig({
  rules: {
    "unicorn/prefer-module": "error",
  },
});

CLI

oxlint --deny unicorn/prefer-module

Version

This rule was added in v1.50.0.

References

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