Ability to pass down custom Chrome settings

Description

Contributor guide

Tech stack

javascriptnodejs

Domain

backendperformance

Issue type

feature

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-3 hours

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

Node.jsunderstanding of Chrome browser flags

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

40

Research direction

Examine the repository's codebase to locate where the Chrome instance is launched (likely in a file like 'src/chrome.js' or similar). Currently, Chrome options are hardcoded. The fix involves adding an optional 'chromeFlags' parameter to the main function or configuration, merging it with default flags, and passing it to Puppeteer's launch method. Check existing tests and documentation to understand the expected API shape.