Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

chore(deps): upgrade Jest past 26 to drop deprecated request/jsdom stack

Open
#449 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
ci-cd, testing-qa

Research direction

Start by running npm ci --legacy-peer-deps and inspecting the Jest dependency tree for request, request-promise-native, and har-validator. Review the Jest configuration and snapshots for changes required by the upgrade, then run the full Jest suite. Done means the deprecated warnings are gone, CI remains green, and the obsolete override is removed only if unused.

Written by the indexing model from the issue text.

Description

dependencies todo :spiral_notepad:

Summary

Jest 26.6.3 pulls jest-environment-jsdom@26jsdom@16 → deprecated:

  • request@2.88.2
  • request-promise-native@1.0.9
  • har-validator@5.1.3

(We already have a narrow overrides.request.qs pin for security; that does not clear the deprecation warnings.)

Parent inventory: #445 (Cluster C).

Scope

  • Upgrade jest, babel-jest, and related test tooling to a line that no longer depends on the deprecated request stack (Jest 28+ with modern jsdom, or at least a jsdom that dropped request).
  • Update Jest config / snapshots if required by the major bump.
  • Keep Node 18 CI (npm ci --legacy-peer-deps) green.

Acceptance criteria

  • No request / request-promise-native / har-validator deprecation warnings on install from the Jest tree
  • Full Jest suite passes
  • Remove obsolete overrides.request only if nothing else still needs it

Related

  • #445 Inventory of npm deprecation warnings
Dominant language
JavaScript
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 multei/web

All issues in multei/web

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.