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
Proxy setting in YLT / PhantomasWrapper.js #78
Comments
Hi @abhishek0001! You are right, there's no way to set up a proxy for the moment. Phantomas can work with proxy settings. But it doesn't send the settings to analyze-css. Analyze-css re-downloads the CSS files one by one, so an improper proxy setting will skip most of the CSS files and give a erroneous score. I opened this issue: macbre/phantomas#500 About the installation process for Windows, I don't really understand what this msvs_version refers to (I'm not a Windows user). Do you mind editing the Wiki to add this mention? That would be great! |
Thanks for the quick answer. I will try and update the wiki soon. For windows installation, YLT uses lwip package which in turn uses node-gyp. node-gyp needs recompilation and needs the msvs_version=2013 flag for locating C++ compiler/libs. Links for more details: |
@gmetais, it took a while, but it's finally there - macbre/phantomas#663 |
You rule @macbre ! |
Fixed by #213. |
Hi,
I tried running YLT in a corporate environment behind a firewall with the git based setup. I kept running into an access denied error.
Adding an option to accept the proxy parameter in PhantomasWrapper.js as a workaround works for me. What is the correct way to set up the corporate proxy with YLT, not sure if this is a bug/missed option?
Thanks
P.S. Can you mention the msvs_version=2013 option to npm install for Windows users for node-gyp setup somewhere in the documentation. Git, bower, npm all need additional proxy set up configuration params too.
The text was updated successfully, but these errors were encountered: