The behavior of no-native has changed #611
Description
The no-native rule changed behavior between eslint 9.27 and 9.28, which is causing CI to fail for this repository.
The following change is the cause of this change:
However, I feel that the current behavior of the rule is correct.
The previous no-native rule reported promises even if they were included in globals.
The no-native rule seems to report promises included in implicit. Therefore, the behavior has changed from before.
However, if you are in an environment where promises cannot be used, I think the correct way to use it is to not include promises in globals.
I'm not sure whether we should modify the no-native rule, or respect the current behavior and modify the no-native tests.
What do you think?