chore(deps): upgrade or remove netlify-cli to clear install deprecations
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- build-system, tooling
Research direction
Start by checking the package manifest, repository scripts, and netlify.toml for current netlify-cli usage, then review the hosting migration context in #416. Choose removal or upgrade, regenerate the lockfile as needed with Node 18 and npm install --legacy-peer-deps, and verify a clean install no longer emits the Cluster A warnings.
Written by the indexing model from the issue text.
Description
Summary
netlify-cli@2.71.0 (devDependency) is the root of a large cluster of npm warn deprecated messages on install, including:
statsd-client,sourcemap-codec,rollup-plugin-inject,rollup-plugin-tersernetlify-plugin-deploy-preview-commenting,node-pre-gyp,tar@4/tar@6,osenvnpmlog/are-we-there-yet/gaugemoize@5/moize@6cli-uxand legacy@oclif/*packages
Parent inventory: #445 (Cluster A).
Options (pick one path)
- Preferred with hosting migration (#416): remove
netlify-clifrom the repo once deploys run on Vercel (and drop Netlify-only scripts/config usage). - Interim: upgrade
netlify-clito a current major that no longer pulls these packages, and regenerate the lockfile with Node 18 +npm install --legacy-peer-deps. - If unused in CI/local workflow: remove it immediately even before #416 completes (verify no scripts/
netlify.tomlhooks require the CLI locally).
Acceptance criteria
- Decide remove vs upgrade (document choice in a PR)
- After change, Cluster A warnings from #445 no longer appear on a clean install
- Document any remaining Netlify CLI usage (or confirm none)
Related
- #416 Migrate hosting from Netlify to Vercel
- #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 5/5 Over a week Newbie friendliness 30/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
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100