Detected not working optional chaining on global variables / optional DOM APIs

Please describe what the rule should do:

eslint should warn me that a browser (without a secure context) can throw and the optional chaining will not save the day:

// Throws an exception in runtime with insecure origin
> caches?.has('anything');
VM262:1 Uncaught ReferenceError: caches is not defined

// Runs without exception in runtime (with secure and insecure origin)
window.caches?.has('anything');

What new ECMAScript feature does this rule relate to? Same for all new APIs which are on the global object.

What category of rule is this? (place an “X” next to just one item)

[x] Warns about a potential error (problem)

Why should this rule be included in ESLint (instead of a plugin)? I dont know. Are you willing to submit a pull request to implement this rule? No, sorry.

[nzakas]

We aren’t moving forward with this, so closing.

[nzakas]

Gotcha. I’m not sold on the need for this being a core rule, though. It doesn’t really seem to rise to the level of must-have for us.