exportsAssignments

Prevent assignment to the exports variable in CommonJS modules.

✅ This rule is included in the node logical preset.

In CommonJS modules, assigning directly to the exports variable breaks the reference to module.exports, which means your exports won’t work as expected. The exports variable is initially a reference to module.exports, but reassigning it creates a new local binding that doesn’t affect the actual module exports.

To export values, always use module.exports directly, or modify properties on exports without reassigning it.

Examples

❌ Incorrect

exports = {};

exports = { foo: 1, bar: 2 };

exports = somethingElse;

✅ Correct

module.exports.foo = 1;

exports.bar = 2;

module.exports = {};

module.exports = exports = {};

exports = module.exports = {};

Options

This rule is not configurable.

When Not To Use It

If you use an unusual code pattern that intentionally needs to remove the original reference to exports, this rule may not be for you. However, doing so may make it harder to understand your code or migrate it to the more modern ECMAScript Modules (ESM) syntax.

Further Reading

• Node.js: Modules - exports shortcut
• Node.js: Modules - module.exports
• CommonJS module system

Equivalents in Other Linters

• ESLint: n/no-exports-assign
• Oxlint: node/no-exports-assign