chromium-bundled image missing Patchright browser binary and all Patchright-dependent routes fail

Routes

NOROUTE

Full routes

NOROUTE

Related documentation

https://docs.rsshub.app/deploy/

What is expected?

Routes requiring browser automation (e.g. /bilibili/user/collection/:uid/:aid) should work in the chromium-bundled image, since that image is specifically meant to include browser support.

What is actually happening?

Any route that uses Patchright for browser automation fails with:

error: Error in /bilibili/user/collection/4963278/380944: Error: browserType.launch: Executable doesn't exist at /root/.cache/ms-playwright/ chromium_headless_shell-1223/chrome-headless-shell-linux64/chrome-headless-shell

╔════════════════════════════════════════════════════════════╗ ║ Looks like Playwright was just installed or updated. ║ ║ Please run the following command to download new browsers: ║ ║ npx playwright install ║ ║ <3 Patchright Team ║ ╚════════════════════════════════════════════════════════════╝

......

Seems like it is patchright npm package, not the official playwright package. I am guessing that the chromium-bundled Dockerfile likely misses the Patchright package? Just my guess.

Deployment information

Self-hosted

Deployment information (for self-hosted)

self-hosted via PikaPods

Additional info

error: Error in /bilibili/user/collection/4963278/380944: Error: browserType.launch: Executable doesn't exist at /root/.cache/ms-playwright/chromium_headless_shell-1223/chrome-headless-shell-linux64/chrome-headless-shell

╔════════════════════════════════════════════════════════════╗

║ Looks like Playwright was just installed or updated.       ║

║ Please run the following command to download new browsers: ║

║                                                            ║

║     npx playwright install                                 ║

║                                                            ║

║ <3 Patchright Team                                         ║

╚════════════════════════════════════════════════════════════╝

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported