`npm run lint` fails when lint script uses `oxlint --format gitlab` instead of ESLint

[medallyon]

After migrating a project from ESLint to oxlint, npm run lint fails at the RTK layer with:

ESLint output (JSON parse failed: EOF while parsing a value at line 1 column 0)

Lint script:

"lint": "tsc --noEmit && oxlint --format gitlab"

oxlint output (when run directly):

[]

Root cause: RTK appears to detect lint or eslint in the command and attempt to parse the output as ESLint JSON. When the command uses oxlint instead, the output format differs and parsing fails.

Expected: RTK passes through oxlint output without attempting ESLint JSON parsing, or detects oxlint commands and applies appropriate filtering.

RTK version: 0.42.0
OS: Windows 11 Pro v10.0.26200
Environment: Claude using Git Bash for Windows

[pszymkowiak]

wshm · Automated triage by AI

🔍 Automated Triage

🐛 Category	bug
🟡 Priority	medium
🎯 Confidence	87%

Summary

RTK incorrectly applies ESLint JSON parsing to oxlint output when npm run lint invokes oxlint; fix by detecting non-ESLint linters and bypassing ESLint-specific output parsing.

This looks like a simple fix that could be auto-resolved. Repo maintainers can use /wshm fix to attempt it.

---

Triaged automatically by wshm · This is an automated analysis, not a human review.