← Back to rules

import/no-default-export Restriction

What it does

Disallow modules from having default exports.

This can help your editor provide better auto-import functionality, as named exports offer more explicit and predictable imports compared to default exports.

Why is this bad?

Default exports can lead to confusion, as the name of the imported value can vary based on how it's imported. This can make refactoring and auto-imports less reliable.

Examples

Examples of incorrect code for this rule:

export default 'bar';

const foo = 'foo';
export { foo as default }

Examples of correct code for this rule:

export const foo = "foo";
export const bar = "bar";

How to use

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

Config (.oxlintrc.json)

{
  "plugins": ["import"],
  "rules": {
    "import/no-default-export": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

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

CLI

oxlint --deny import/no-default-export --import-plugin

Version

This rule was added in v0.2.14.

References

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