You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eslint-scope expects 3, 5, 6, 7, ... 13 as ecmaVersion. Those are the values eslint-scope is currently getting from ESLint, and all eslint-scope tests are based on those values.
After we merge and release eslint/eslint#15185, ESLint will be passing 3, 5, 2015, 2016, ... 2022 as ecmaVersion to eslint-scope, regardless of the mode (eslintrc or flat config).
This should work the same as it was working before, because eslint-scope uses ecmaVersion only to check if it is >= 5, and >= 6:
So, any of 6, 7, 8, 9, 10, 11, 12, 13, 2015, 2016, 2017, 2018, 2019, 2020, 2021, and 2022 will work the same, as they're all >= 5 and >= 6.
However, it would be good to add some tests with the new values, to confirm this behavior and make sure that it won't break after future changes to eslint-scope.
The text was updated successfully, but these errors were encountered:
ref: eslint/eslint#15185 (comment)
eslint-scope expects 3, 5, 6, 7, ... 13 as
ecmaVersion
. Those are the values eslint-scope is currently getting from ESLint, and all eslint-scope tests are based on those values.After we merge and release eslint/eslint#15185, ESLint will be passing 3, 5, 2015, 2016, ... 2022 as
ecmaVersion
to eslint-scope, regardless of the mode (eslintrc or flat config).This should work the same as it was working before, because eslint-scope uses
ecmaVersion
only to check if it is>= 5
, and>= 6
:eslint-scope/lib/scope-manager.js
Lines 80 to 82 in e57ffb0
eslint-scope/lib/scope-manager.js
Lines 248 to 250 in e57ffb0
So, any of 6, 7, 8, 9, 10, 11, 12, 13, 2015, 2016, 2017, 2018, 2019, 2020, 2021, and 2022 will work the same, as they're all
>= 5
and>= 6
.However, it would be good to add some tests with the new values, to confirm this behavior and make sure that it won't break after future changes to eslint-scope.
The text was updated successfully, but these errors were encountered: