Rule Change: no-implicit-globals should not report exported

What rule do you want to change?

no-implicit-globals

What change to do you want to make?

Implement suggestions

How do you think the change should be implemented?

A new default behavior

Example code

/* exported testFunc */

/**
 * @returns {int}
 */
function testFunc() {
    "use strict";

    return 1 + 2;
}

What does the rule currently do for this code?

When using with lexicalBindings /*eslint no-implicit-globals: ["error", {"lexicalBindings": true}]*/ it gives an error

What will the rule do after it’s changed?

Not report an error, if the variable/function is “exported”

Additional comments

This was already requested previously but closed due to age https://github.com/eslint/eslint/issues/10066

Essentially it should have the same behavior as rule no-unused-vars, where exported variables/functions don’t count as unused

[mdjermanovic]

Not report an error, if the variable/function is “exported”

Makes sense to me 👍

I think the main purpose of this rule is to prevent accidental creation of global variables. Declaring /* exported testFunc */ indicates the intention to create a global testFunc, and would be an alternative to the style window.testFunc = function (){} that this rule currently enforces.

[nzakas]

However, if this requires adding a new property on Variable objects (https://github.com/eslint/eslint/pull/16343#discussion_r978961061), then it seems more appropriate to mark the change as a feat, as it will include an addition to the core.

Sounds good.