build: fix broken ESLint setup and missing prettier plugin

Open Beginner friendly
#669 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
eslint, typescript
Domain
build-system, tooling

Research direction

Start with package.json and .eslintrc, then run yarn lint to reproduce the missing-plugin and Prettier compatibility errors. Check the listed devDependencies and configuration entries against the requested versions and cleanup; done means yarn lint completes successfully across the codebase.

Written by the indexing model from the issue text.

Description

Bug Description

Running yarn lint crashes completely with the error ESLint couldn't find the plugin "eslint-plugin-prettier".

This happens because .eslintrc configures the prettier plugin ("plugins": ["prettier"] and "prettier/prettier": ["error"]), but eslint-plugin-prettier was never added to devDependencies in package.json. Additionally, .eslintrc contains leftover boilerplate ignorePatterns referencing packages/preload/... from an unrelated project template.

Proposed Solution
  • Add "eslint-plugin-prettier": "^4.2.1" to devDependencies in package.json.
  • Keep prettier at 2.8.8 but downgrade prettier-plugin-tailwindcss to ^0.2.8 to maintain compatibility with Prettier 2.x and resolve the prettier/plugins/angular module missing error.
  • Remove invalid ignorePatterns from .eslintrc.
  • Verified that yarn lint now successfully runs across the codebase. I will submit a PR for this!
Dominant language
TypeScript
Stars
108
Forks
188
Avg merge
3d 14h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from containers/podman.io

All issues in containers/podman.io

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.