claude[bot] a101449cba Fix: Make SingleFile use SINGLEFILE_CHROME_ARGS with fallback to CHROME_ARGS ...

This fix resolves issue #1445 where SingleFile was not respecting Chrome
user data directory and other Chrome launch options that work for other
Chrome-based extractors (PDF, Screenshot, etc.).

Changes:
- Added SINGLEFILE_CHROME_ARGS config option in config.json with x-fallback
  to CHROME_ARGS
- Updated SingleFile extractor to read and pass Chrome arguments via
  --browser-args parameter
- Updated docstring to document the new environment variable

This ensures SingleFile respects the same Chrome configuration (user data
directory, cookies, etc.) as other Chrome-based extractors.

Fixes #1445

Co-authored-by: Nick Sweeting <pirate@users.noreply.github.com>

2025-12-29 22:39:48 +00:00

..

templates

improve plugin tests and config

2025-12-29 00:45:23 -08:00

tests

improve plugin tests and config

2025-12-29 00:45:23 -08:00

binaries.jsonl

way better plugin hooks system wip

2025-12-28 03:39:59 -08:00

config.json

Fix: Make SingleFile use SINGLEFILE_CHROME_ARGS with fallback to CHROME_ARGS

2025-12-29 22:39:48 +00:00

on_Crawl__04_singlefile.js

improve plugin tests and config

2025-12-29 00:45:23 -08:00

on_Snapshot__50_singlefile.py

Fix: Make SingleFile use SINGLEFILE_CHROME_ARGS with fallback to CHROME_ARGS

2025-12-29 22:39:48 +00:00