-
Notifications
You must be signed in to change notification settings - Fork 200
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
polymer-cli is huge and very slow to install #2583
Comments
Also since 1.6 there is Also |
Hi, is there any update? |
Hello, i have been trying to install polymer-cli since a hour and it is not installed yet. I used command |
I recommend using |
Thanks @davidmaxwaterman It worked! |
Installing polymer-cli today took over 30 minutes on my machine with a business internet connection. There were not any errors in --verbose. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We currently have a build which runs on VSTS online (visual studio), it installs polymer-cli globally per build.
While this is inefficient and we should probably cache global deps across some builds, it doesn't excuse the fact that polymer-cli takes us 9 minutes to install.
Looking at the dependency tree, apparently (according to cost-of-modules util):
web-component-tester dependencies:
so is this dependency size pretty much because we have differing versions of our own repos across other repos? if all polymer-* projects had the same dependencies exactly, would we have one copy of each and the size would go down? (in this case you'd save 101M from WCT's second polymer-build)
on top of this, installing wct of course results in downloading the sauce binary, but that shouldn't be so slow as it is only ~6MB.
thoughts?
The text was updated successfully, but these errors were encountered: