Skip to content
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

npm install / yarn add playwright takes forever #2265

Closed
nojvek opened this issue May 16, 2020 · 6 comments
Closed

npm install / yarn add playwright takes forever #2265

nojvek opened this issue May 16, 2020 · 6 comments

Comments

@nojvek
Copy link

nojvek commented May 16, 2020

I spent at-least 30 mins waiting for the spinner. This seems like a massive dependency. How do I speed it up? I already have chrome, firefox and safari on my machine.

How do I make playwright use existing versions?

@mxschmitt
Copy link
Member

mxschmitt commented May 16, 2020

The recent Playwright versions will reuse the downloaded versions. Which operating system are you using? And which Playwright version?

Also a generic speedtest would be useful.

@nojvek
Copy link
Author

nojvek commented May 16, 2020

I just did yarn add so whatever is latest published version.

Using Mac on Catalina. It took 45 mins but seemed to work now.

Having the getting started script work out of the box was a massive revelation. Wow! This is indeed a fantastic library.

@pavelfeldman
Copy link
Member

First time Playwright is installed it fetches the browsers off CDNs (~450Mb). Could be the CDN outage or CDN throttling on your side...

@aslushnikov
Copy link
Collaborator

How do I make playwright use existing versions?

@nojvek as of today (May 2020), Playwright has to download browsers from CDN since we distribute our own builds of webkit and firefox.

Using Mac on Catalina. It took 45 mins but seemed to work now.

That's crazy! Looks like an occasional internet problem to me. It usually takes <30 seconds for me to download browsers.

That said, Playwright caches downloaded browsers on your machine, so you'll need to do it only once.

@nojvek
Copy link
Author

nojvek commented May 17, 2020

I know this is closed and thanks to responding to me at owl o’ clock.

One thing that could make the install user experience nicer is printing something to the console e.g downloading of the browser do user just doesn’t see spinner for >30s.

@arjunattam
Copy link
Contributor

Thanks for pointing this out @nojvek. It seems that yarn add suppresses stdout/stderr output from postinstall scripts, causing the install progress to be hidden (relevant issue).

Screen Shot 2020-05-17 at 10 54 48 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants