refactor: update headless flag from `true` to `new`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 47/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
Search the project for Puppeteer launch calls that set headless: true; start by checking the relevant configuration and tests that exercise browser startup. Update the flag to headless: "new" and run the affected tests to confirm the deprecation warning is gone. The issue names no file or test, and it has had no activity for over three years.
Written by the indexing model from the issue text.
Description
Currently we get a warning because of a deprecated flag for headless mode.
Puppeteer old Headless deprecation warning:
In the near feature `headless: true` will default to the new Headless mode
for Chrome instead of the old Headless implementation. For more
information, please see https://developer.chrome.com/articles/new-headless/.
Consider opting in early by passing `headless: "new"` to `puppeteer.launch()`
If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.
By updating the value we can get rid of the warning and are save in the future
- Dominant language
- HTML
- Stars
- 131
- Forks
- 7
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 42
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 push-based/user-flow
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
push-based/user-flow#356 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
push-based/user-flow#355 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 24/100
push-based/user-flow#285 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
push-based/user-flow#272 · 1 comment ·
Maintainers usually reply within 1 day
-
nx-plugin - init command adds `"PLUGIN_NAME": "^0.0.0"` to `package.json`May be free again @ChristopherPHolder claimed this 1212 days ago, and no pull request is open. Openbug DX
push-based/user-flow#248 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in push-based/user-flow
Similar issues
-
area: ops bug complexity: trivial
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
accensa/x402-facilitator-stellar#773 ·
Maintainers usually reply within 1 day
-
[Bug / Enhancement]: Improve teleop_robot CLI with configurable timeout, robust input validation, and clean ROS shutdownPossibly taken @muskan-creates352 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
console enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
MFisher14/ctf-flightdeck#39 ·
-
CLI: expose public search language with --languagePossibly taken @semajzandrews claimed this today. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
evener-transcript-v2-upgrade tool still scans transcript files through bufio's 4 KiB default bufferOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
prime-radiant-inc/evener#6370 ·
Maintainers usually reply within 1 day