-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support for Raspberry PI #4984
Comments
@mxschmitt For Raspberry PI there is aarch64 which is the new unstable version and armhf which is the older, curious to know which architectures are the part of this issue ? |
I'll close this as not a goal for now. |
I would love to see this! Have a PI I want to delegate some browser testing stuff to. |
I made a Dockerfile to install playwright-python on Raspberry pi (chrome only). |
I am very interested in this 👍 |
Is there a way to get it working for webkit as well since you were able to get it working with Chromium? @YNedderhoff also appears to be interested in this (microsoft/playwright-java#399) |
I'm running raspbian on a raspberry pi 4b and changed the path playwright looks for chromium to the default chromium web browser that is included with raspbian. Playwright still expects to find chrome in /chromium-901522/chrome-linux so I just added those directories and moved all the files into the chrome-linux directory so the path looks like /usr/lib/chromium/chromium-901522/chrome-linux. You will also have to rename the file "chromium" to "chrome". Then I just use PLAYWRIGHT_BROWSERS_PATH=/usr/lib/chromium node yourapphere.js. I imagine you could just copy the included chromium files somewhere else too as changing the directories makes it so the web browser no longer points to chromium. |
For the record: Playwright v1.17+ supports Raspberry PI with arm - see 1.17 release notes |
Issue to see if there is an interest in using it on a Raspberry PI / ARM.
Changes required: Add custom build targets.
Please vote up if so. 👍
Came up here:
The text was updated successfully, but these errors were encountered: