How to manually specify path to browser that should be ...

At a glance

The community member is experiencing an issue with their Playwright setup after restarting their app on AWS Elastic Beanstalk. The error message indicates that the Chromium executable is missing from the expected location. The community member is using the crawlee package version 3.7.2 and Playwright version 1.4.1, and is unsure if this is the cause of the issue.

In the comments, another community member suggests updating to the latest versions of crawlee and Playwright, and also trying to use playwright: "*" in the package.json file.

WWojciech

I have a problem with my playwright after restarting app on AWS EB as you can see

Plain Text

Mar  7 15:20:22 ip-10-249-15-251 web: at async /var/app/current/node_modules/@crawlee/browser-pool/browser-pool.js:274:37 {
Mar  7 15:20:22 ip-10-249-15-251 web: name: 'BrowserLaunchError',
Mar  7 15:20:22 ip-10-249-15-251 web: [cause]: browserType.launchPersistentContext: Executable doesn't exist at /home/webapp/.cache/ms-playwright/ch                                    romium-1097/chrome-linux/chrome

my app is trying to run chromium under above path, but I don't have that version installed

I have this:

Plain Text

sh-4.2$ pwd
/home/webapp/.cache/ms-playwright
sh-4.2$ ls
chromium-1105  ffmpeg-1009

I'm not sure why this is happening

is this because im using meta package crawlee: 3.7.2 without caret (^) and underneath its updated to the newest version?
also playwright: 1.4.1 where newest is 1.4.2

1 comment

OOleg V.

Try to update to latest crawlee and playwright versions.
Also try to use playwright: "*" in package.json

Add a reply

Apify Discord Mirror

How to manually specify path to browser that should be run?