Summary
The npm run lint pipeline is completely broken. ESLint is referenced in package.json scripts but is not listed in devDependencies, causing sh: eslint: command not found when attempting to run linting.
Issue Details
- Error:
npm run lint exits with code 127 (command not found)
- Root Cause: eslint is not in package.json devDependencies
- Impact: Lint validation cannot run in CI/CD or locally; recent 28 merged PRs were not linted
Fix Required
Add eslint to devDependencies:
{
"devDependencies": {
"eslint": "^10.0.3"
}
}
Then run npm install and verify npm run lint succeeds.
Additional Context
- TypeScript type checking: ✅ PASS
- Build: ✅ PASS
- Lint: ❌ FAIL (eslint not found)
- Tests: Not configured
A quality audit report has been generated at knowledge/quality/design-system-audit.md
Priority: CRITICAL
Summary
The
npm run lintpipeline is completely broken. ESLint is referenced in package.json scripts but is not listed in devDependencies, causingsh: eslint: command not foundwhen attempting to run linting.Issue Details
npm run lintexits with code 127 (command not found)Fix Required
Add eslint to devDependencies:
{ "devDependencies": { "eslint": "^10.0.3" } }Then run
npm installand verifynpm run lintsucceeds.Additional Context
A quality audit report has been generated at
knowledge/quality/design-system-audit.mdPriority: CRITICAL