Migrate PhantomJS to Headless Chrome

Description

This issue does not include a description.

Contributor guide

Tech stack

javascriptnodejs

Domain

backend

Issue type

refactor

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

familiarity with Node.jsunderstanding of headless browser basics

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Review the codebase to locate all PhantomJS usage, particularly in screenshot and scraping modules. Replace with Headless Chrome (e.g., Puppeteer). Update package.json and ensure all existing tests pass. Check for any PhantomJS specific APIs that may need to be adapted.