Skip to content

fix(ci): resolve ESLint parsing errors for test files#33

Open
quinnjr wants to merge 1 commit intomainfrom
hotfix/fix-release-workflow
Open

fix(ci): resolve ESLint parsing errors for test files#33
quinnjr wants to merge 1 commit intomainfrom
hotfix/fix-release-workflow

Conversation

@quinnjr
Copy link
Contributor

@quinnjr quinnjr commented Feb 17, 2026

Summary

  • Create tsconfig.eslint.json that includes test files, fixing 4 ESLint parsing errors
  • Point ESLint parserOptions.project to the new tsconfig
  • Fix unused variable errors with underscore prefixes
  • Add varsIgnorePattern and caughtErrorsIgnorePattern to no-unused-vars rule
  • Add missing @eslint/js devDependency

Root Cause

tsconfig.json excludes **/*.test.ts (correct for build), but ESLint's parserOptions.project pointed to it, making type-aware linting impossible for test files.

Test plan

  • CI lint job passes (0 errors)
  • pnpm exec eslint src/ succeeds locally with 0 errors

The CI lint job fails because parserOptions.project points to
tsconfig.json, which explicitly excludes *.test.ts files. ESLint's
typescript parser cannot resolve type information for test files,
causing 4 parsing errors.

Create tsconfig.eslint.json that extends the base config but includes
test files. Point ESLint's parserOptions.project to this new config.

Also fix unused variable errors:
- Prefix catch clause variable with underscore (_userinfoError)
- Prefix side-effect-only variable with underscore (_server)
- Add varsIgnorePattern and caughtErrorsIgnorePattern to the
  no-unused-vars rule to match the existing argsIgnorePattern
- Add missing @eslint/js devDependency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant