What's pending across every project
1 open · sorted by priority then due-date
Filtered by tag eslint clear
note
Correction: fix-plan item 2.2 (ESLint) had the wrong cause — do not act on its original wording
The consolidated fix plan says of ESLint: "--eslintrc was removed in v9; remove the flag or pin ESLint 8."
That is wrong. The platform already pins ESLint 8 in the node image. The real fault, found by the team in 77f8b9d14 (TP-5958), was binary resolution: `npx eslint` resolved the REPOSITORY's ./node_modules/.bin/eslint — version 9 — which rejects the flag the image pin still requires.
Removing the flag, as the plan advised, would have broken the image's ESLint 8 behaviour. Anyone acting on the plan's original wording should stop and read 77f8b9d14 instead.
Note this does NOT address fix-plan item 2.3, the missing JSX parser — no ESLint configuration file is touched in the 53 files changed between qa and dev, so React frontends still return "Unexpected token <".
77f8b9dTP-5958backend/wb-cpu-worker/app/analyzers/javascript/_eslint_common.py
Testable (Pramora)
· testable-platform
· by saravanan@scrumclaw.ai
9d ago
09-29 16:27
09-29 16:27