Implicit Globals vs Declaration Enforcement: no‑implicit‑globals vs no‑var

Scope

In projects that exclusively use ES modules, the no-implicit-globals rule still flags top‑level function declarations as implicit globals, even though module scope prevents global leakage.

Unresolved Behavior

The rule’s documentation states it is intended for scripts, but its implementation does not automatically detect sourceType. This leads to false positives when the configuration uses sourceType: "module".

Decision Point

Should top‑level function declarations in modules be exempt from the warning, or should the rule enforce a stricter declaration style regardless of module boundaries?

• What is the intended behavior of no-implicit-globals regarding top‑level function declarations in ES modules?
• Will future ESLint releases modify the rule to detect sourceType automatically?
• Is there an open issue tracking this ambiguity?