Skip to content

Resolve Lint Errors Across Packages and Strengthen CI Enforcement #4700

@quiet-node

Description

@quiet-node

Problem

All four packages in the repository currently have numerous lint errors. Running npm run lint in any package reveals extensive ESLint violations, which hinders the development process. Developers encounter these errors even when their changes do not touch the affected areas, leading to distractions and potential clutter in code reviews.

Goals

  • Resolve all lint errors across the entire codebase.
  • Ensure successful TypeScript typechecking in all packages.
  • Apply eslint --fix where possible to auto-correct fixable issues.
  • Strengthen the CI pipeline to catch and fail on lint issues for entire repo for every pull request.

Acceptance Criteria

  • npm run lint passes in all packages without errors.
  • npm run typecheck (or equivalent) succeeds in all packages.
  • CI jobs include lint checks that block PR merges on failures.
  • No regressions in existing functionality or tests.

Metadata

Metadata

Assignees

Labels

Good First IssueIssues which are ideal for a first time or new project contributor.P3enhancementNew feature or request

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions