chore(deps): remove unused gatsby-image dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
npm warn deprecated gatsby-image@2.11.0 appears on install. The package is a direct dependency in package.json (gatsby-image@2.11.0) but is not imported anywhere under src/ (no gatsby-image, GatsbyImage, or StaticImage usage).
Upstream guidance: migrate to gatsby-plugin-image — but for this repo the simplest fix is to remove the unused dependency.
Parent inventory: #445 (Cluster B quick win).
Acceptance criteria
- Remove
gatsby-imagefrompackage.json/ lockfile - Confirm no remaining imports or GraphQL fragments that require it
-
npm install --legacy-peer-depsno longer warns aboutgatsby-image - Existing Jest suite stays green
Notes
If image components are reintroduced later under Gatsby, use gatsby-plugin-image (or Next.js Image after #415).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json and the lockfile, then search src/ for gatsby-image, GatsbyImage, StaticImage, and related GraphQL fragments. Remove the unused dependency, run npm install --legacy-peer-deps, and run the existing Jest suite; done means no matching usage remains, the install warning is gone, and tests stay green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100