← Back to rules

import/no-mutable-exports Style

What it does

Forbids the use of mutable exports with var or let.

Why is this bad?

In general, we should always export constants

Examples

Examples of incorrect code for this rule:

export let count = 2;
export var count = 3;

let count = 4;
export { count };

Examples of correct code for this rule:

export const count = 1;
export function getCount() {}
export class Counter {}

Functions/Classes

Note that exported function/class declaration identifiers may be reassigned, but are not flagged by this rule at this time. They may be in the future.

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-mutable-exports": "error"
  }
}

Config (oxlint.config.ts)

import { defineConfig } from "oxlint";

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

CLI

oxlint --deny import/no-mutable-exports --import-plugin

Version

This rule was added in v0.15.13.

References

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