[core] fix: allow browser globals in config files #3992
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The config checker previously only allowed Node.js globals, but since the config file runs also in the browser context, users should be able to access browser APIs like
documentorwindowwhen needed.This was incorrectly flagged as an error by the
no-undefESLint rule. The fix adds browser globals to the allowed globals in the linter config.Fixes #3990.