Open spidy0x0 opened 3 years ago
It looks like Playright needs to execute pre (or post) install scripts, which aren't supported in Stackblitz.
Hi @spidyhackx! This will not just work out of the box. The problem here is that in order to run Playwright, or even Puppeteer, you need a binary that will not just work in the browser. We can't just execute any arbitrary binary in WebContainer as everything still runs in the browser.
We are looking at possible solutions to get something like Puppeteer/Playwright working within StackBlitz, but we are not there yet and it's still ideas, so no active development on that front yet.
Hi together, I've been tinkering with this, and seem to have gotten a bit further, but chromium still times out on launching for me.
I'm using chrome-aws-lambda
and playwright-core
. After installing these dependencies, there will be a google-chrome
binary in /usr/local/bin/
. If yuo manually specify that as the executablePath
argument, you'll get past the issue mentioned in the OP.
The problem then becomes one of chromium seemingly timing out on launching. I've messed with a few chromium flags, but to no avail.
For more details, see: https://stackblitz.com/edit/node-riv6gt?file=index.js
Describe the bug: Playwright is a browser automation tool . but its failing on startup
Steps to reproduce:
Expected behavior: Open browser interface
Desktop :
Additional context:
Also, https://turbo.sh/install-scripts is not working