globals

Hey hey! This is more of a question than a request, and I'm happy to open the PR myself if you think this would fit in the repository. Thunderbird supports the Web Extension API, but encourages using the global instead of the global, as this is more fitting for email client. In Thunderbird, all WebExtension API can be accessed through the namespace, as with Firefox, but also through the namespace, which is a better fit for Thunderbird. — Thunderbird Developer Documentation: Using WebExtension APIs Could it make sense to introduce a category to include this global, or is it too niche/vendor-specific? This wouldn't reduce the configuration size for downstream projects, as is the only global afaik. So the only gain is that by a user delegating this to , users will know all globals are covered.

We are currently using CubeJs to run and maintain Data Models and run a semantic layer for the data analytics in production env. We are adding eslint for the JS files used in the applications, and it seems the applications seems to have it's own set of global variables. It would be nice to include those in the config specific for cube.

Rstest is a JavaScript testing framework similar to Jest and Vitest. This PR adds the global APIs exposed by its configuration to this package, maintained manually because Rstest currently does not provide an ESLint plugin. Related Links Rstest documentation https://github.com/web-infra-dev/rstest