chore(deps): clear Gatsby 2 transitive npm deprecation warnings
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, next.js, node.js, webpack
- Domain
- build-system, ci-cd, web-dev
Research direction
Start with parent inventory #445, then review #415 and the open or blocked upgrade PRs #421, #413, #432, and #444 to choose the Gatsby-to-Next.js migration or coordinated Gatsby upgrade. Done means the selected implementing PR(s) are linked, Cluster B warnings disappear on a clean install, and build/test CI stays green on Node 18.
Written by the indexing model from the issue text.
Description
Summary
Most remaining install deprecations come from the Gatsby 2 / webpack 4 stack ([email protected] and plugins), not from app source. Examples:
urix/resolve-url(webpack4 → micromatch → snapdragon → source-map-resolve)[email protected]@hapi/joi@15and related@hapi/*(gatsby + workbox viagatsby-plugin-offline)[email protected](webpack-dev-server@3)- old
rimraf/glob@7/core-js@2/[email protected]/uuid@3under Gatsby tooling - older
npmlogviasharpundergatsby-plugin-manifest
Leaf-level overrides will not sustainably clear this set.
Parent inventory: #445 (Cluster B).
Recommended paths (in order of preference)
- Long-term: complete #415 (Gatsby → Next.js) — removes the entire cluster.
- Medium-term: coordinated Gatsby major upgrade (see open/blocked PRs #421, #413, #432, #444) with matching plugin majors.
- Avoid: one-off overrides for every deprecated leaf package.
Acceptance criteria
- Choose path 1 or 2 and link the implementing PR(s)
- After landing, Cluster B warnings from #445 are gone on a clean install
- Build/test CI remains green on Node 18
Related
- #415 Migrate site from Gatsby to Next.js
- #446 Remove unused
gatsby-image(quick win, independent) - #445 Inventory of npm deprecation warnings
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
More from multei/web
-
dependencies todo :spiral_notepad:
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
dependencies todo :spiral_notepad:
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
dependencies todo :spiral_notepad:
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
dependencies todo :spiral_notepad:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
TheOdinProject/curriculum#31423 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
WGBH-MLA/dream-aapb#69 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Mintplex-Labs/anything-llm#6490 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
openlayers/ol-cesium#1364 ·