gajus/usus

Ability to pass down custom Chrome settings

Open

#29 opened on Aug 30, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (33 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (800 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

It would be great if it was possible to pass down custom chrome settings (like --no-sandbox) without having to create and maintain the actual Chrome instance itself.

Contributor guide

Research direction
Look for where Chrome is launched in the codebase, typically using Puppeteer or similar. Add a configuration option to pass custom launch arguments.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70