Disallow the assignment to `exports` (`n/no-exports-assign`)

💼 This rule is enabled in the following configs: 🟢 recommended-module, ✅ recommended-script.

To assign to exports variable would not work as expected.

// This assigned object is not exported.
// You need to use `module.exports = { ... }`.
exports = {
    foo: 1
}

📖 Rule Details

This rule is aimed at disallowing exports = {}, but allows module.exports = exports = {} to avoid conflict with n/exports-style rule's allowBatchAssign option.

👍 Examples of correct code for this rule:

/*eslint n/no-exports-assign: error */

module.exports.foo = 1
exports.bar = 2

module.exports = {}

// allows `exports = {}` if along with `module.exports =`
module.exports = exports = {}
exports = module.exports = {}

👎 Examples of incorrect code for this rule:

/*eslint n/no-exports-assign: error */

exports = {}

🔎 Implementation

Rule source
Test source

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!