Enabling globals only for part of a file

@platinumazure suggested that I open this issue. I’m not sure which template it fits, so I’m just beginning discussion.

In the example below puppeteer uses window, document etc in Node without providing them as function parameters, and I don’t want ESLint to complain about that, but I also don’t want them available outside the puppeteer functions which use them. I tried to fix it using directives:

const results = await page.evaluate(selector => {
  /* global document:readonly */
  const titleNodes = [...document.querySelectorAll(selector)];
  const titles = titleNodes
    .filter(node => node.textContent.includes('. '))
    .map(node => node.textContent.trim());
  return titles;
  /* global document:off */
}, selector);

However, those directives don’t work as I thought they would. Apparently, they only apply to the entire file, unlike

/* eslint-disable rule */
// targeted code
/* eslint-enable rule */

@platinumazure suggested no-undef as a workaround, but I want more precision than that.

I’m wondering if this can be solved as a new option related to globals on the no-undef rule or something entirely different.

What are your thoughts?

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.

[jsejcksn]

@eslint I know you don’t really mean that.