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
While upgrading eslint-bridge's ESLint dependencies (see #3631), we are currently stuck with ESLint 8.26.0 and we cannot safely upgrade further without substantial changes on the way we configure and use ESLint Linter API.
ESLint 8.27.0 introduced a breaking change with eslint#16458 on a few rules - including comma-dangle - based on ESLint new experimental configuration system (see part 1, part2, and part 3).
This change triggers the following runtime error on eslint-bridge:
A few core rules retrieving the parser options from the rule context were updated, and this commit is the root cause of the above failure, which is tightly coupled with ESLint's new configuration system.
I was not able to figure out a quick workaround, and as of now, it seems that we to adopt the new experimental configuration system, which would require quite some change on the overall approach of linting configuration.
The purpose of this ticket is to investigate and adopt ESLint new configuration system in order to be able to upgrade further ESLint dependencies. There could be another (easier) solution that we would prevent us from changing how we configure the linter.
The text was updated successfully, but these errors were encountered:
While upgrading eslint-bridge's ESLint dependencies (see #3631), we are currently stuck with ESLint 8.26.0 and we cannot safely upgrade further without substantial changes on the way we configure and use ESLint Linter API.
ESLint 8.27.0 introduced a breaking change with eslint#16458 on a few rules - including
comma-dangle
- based on ESLint new experimental configuration system (see part 1, part2, and part 3).This change triggers the following runtime error on eslint-bridge:
A few core rules retrieving the parser options from the rule context were updated, and this commit is the root cause of the above failure, which is tightly coupled with ESLint's new configuration system.
ESLint article about the new configuration system mentions that we can no longer use
defineRule()
,defineRules()
, andgetRules()
when usingLinter
, which happens to be our case.I was not able to figure out a quick workaround, and as of now, it seems that we to adopt the new experimental configuration system, which would require quite some change on the overall approach of linting configuration.
The purpose of this ticket is to investigate and adopt ESLint new configuration system in order to be able to upgrade further ESLint dependencies. There could be another (easier) solution that we would prevent us from changing how we configure the linter.
The text was updated successfully, but these errors were encountered: