chore(deps): clear npm install deprecation warnings
Open
Nobody has claimed this yet.
dependencies
todo :spiral_notepad:
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Context
npm install prints a large set of npm warn deprecated … messages. Almost all come from a few root packages; patching leaf packages one-by-one is ineffective.
This issue inventories the warnings and maps each cluster to a remediation issue (existing or new).
Inventory (warning → pulled by → remediation)
Cluster A — netlify-cli@2.71.0 (devDependency)
| Deprecated package | Path (abbrev.) | Remediation |
|---|---|---|
statsd-client@0.4.5 |
netlify-cli → @netlify/build |
#447 / #416 |
sourcemap-codec@1.4.8 |
netlify-cli → @netlify/plugin-edge-handlers → magic-string |
#447 / #416 |
rollup-plugin-inject@3.0.2 |
same edge-handlers / rollup polyfills | #447 / #416 |
rollup-plugin-terser@7.0.2 |
same | #447 / #416 |
netlify-plugin-deploy-preview-commenting@0.0.1-alpha.16 |
@netlify/build |
#447 / #416 |
node-pre-gyp@0.13.0 |
@vercel/nft via zip-it |
#447 / #416 |
tar@4.4.19 / tar@6.2.1 |
node-pre-gyp / @mapbox/node-pre-gyp |
#447 / #416 |
osenv@0.1.5 |
node-pre-gyp → nopt |
#447 / #416 |
npmlog / are-we-there-yet / gauge |
node-pre-gyp / @mapbox/node-pre-gyp |
#447 / #416 |
moize@5 / moize@6 |
@netlify/build |
#447 / #416 |
cli-ux@5 + @oclif/* |
netlify-cli oclif stack |
#447 / #416 |
debug@4.1.1 (also Gatsby) |
https-proxy-agent under netlify-cli |
#447 / #416 |
Cluster B — Gatsby 2 / webpack 4 stack (gatsby@2.32.13 + plugins)
| Deprecated package | Path (abbrev.) | Remediation |
|---|---|---|
urix@0.1.0 / resolve-url@0.2.1 |
webpack4 → micromatch → snapdragon → source-map-resolve | #448 / #415 |
eslint-loader@2.2.1 |
gatsby |
#448 / #415 |
@hapi/joi@15 + @hapi/{hoek,topo,bourne,address} |
gatsby / gatsby-plugin-offline → workbox |
#448 / #415 |
chokidar@2.1.8 |
webpack-dev-server@3 |
#448 / #415 |
rimraf@2.x / glob@7.x |
eslint-loader, cacache, workbox, plugins | #448 / #415 |
core-js@2.6.11 |
workbox → babel-runtime | #448 / #415 |
debug@4.1.1 |
gatsby typescript-eslint / engine.io | #448 / #415 |
uuid@3 (telemetry / sharp tooling) |
gatsby-plugin-sharp / gatsby-cli | #448 / #415 |
npmlog (older) |
sharp via gatsby-plugin-manifest |
#448 / #415 |
gatsby-image@2.11.0 |
direct dependency (unused in src) | #446 |
Related blocked upgrade PRs: #421, #413, #432, #444. Long-term destination: #415 (Gatsby → Next.js).
Cluster C — Jest 26 / jsdom 16
| Deprecated package | Path (abbrev.) | Remediation |
|---|---|---|
request@2.88.2 |
jest → jsdom | #449 |
request-promise-native@1.0.9 |
same | #449 |
har-validator@5.1.3 |
request |
#449 |
Cluster D — Material UI v4
| Deprecated package | Path (abbrev.) | Remediation |
|---|---|---|
popper.js@1.16.1 |
@material-ui/core |
#436 |
Cluster E — other tooling (lower priority / secondary)
| Deprecated package | Path (abbrev.) | Notes |
|---|---|---|
uuid@8.3.2 |
codecov, cypress → @cypress/request |
Revisit when upgrading codecov / Cypress peers; not blocking install |
glob@7 / rimraf@3 |
@stryker-mutator/core@4 |
Optional: upgrade or drop Stryker if unused in CI |
Acceptance criteria
- Each cluster has a dedicated remediation issue (or an existing issue that owns it)
- Cluster A → #447 (and/or #416)
- Cluster B → #448 (and/or #415); quick win
gatsby-image→ #446 - Cluster C → #449
- Cluster D → #436
- Quick wins landed where safe (e.g. unused
gatsby-imagein #446) - After remediations, a fresh
npm install --legacy-peer-depsno longer prints the Cluster A–D warnings above (Cluster E optional) - Do not silence warnings with
loglevel/ ignore flags — fix or remove the root packages
Notes
- Prefer fixing root packages over
overridesfor every leaf deprecation. - Hosting migration (#416) naturally drops Cluster A if
netlify-cliis removed from the repo. - Framework migration (#415) naturally drops Cluster B.
Child issues
- #446 remove unused
gatsby-image - #447 upgrade or remove
netlify-cli - #448 clear Gatsby 2 transitive deprecations
- #449 upgrade Jest past 26
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 by running npm install --legacy-peer-deps and compare the deprecation warnings with the Cluster A–D inventory. Review the root dependencies and the child issues #446–#449, then verify that each cluster has an owning remediation and that a fresh install no longer reports those warnings; Cluster E is optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100