Skip to content

Can we set proxy or use a environment variable of download url when download the prebuilt binary #605

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
rrandom opened this issue Mar 25, 2019 · 5 comments

Comments

@rrandom
Copy link

rrandom commented Mar 25, 2019

💡 Feature description

When the network condition is not good, could wasm-pack set the proxy of curl, or using a environment variable of the download url? just like SASS_BINARY_SITE for node-sass

💻 Basic example

Include a basic code example if possible. Omit this section if not applicable.

@ashleygwilliams
Copy link
Member

hi @rrandom ! are you familiar with the --mode no-install? this will allow you to skip your install and will simply expect that the required tools are in path. would this fulfill your requirements?

@rrandom
Copy link
Author

rrandom commented Mar 29, 2019

@ashleygwilliams Thanks for pointing out. I thinks it enough now

@ashleygwilliams
Copy link
Member

great to hear! i'll close, but please file again if you have any ideas on making that experience better!

@toymil
Copy link

toymil commented Nov 21, 2023

Hi @ashleygwilliams , in the case of headless chrome what should I do?

wasm-pack can't download chromedriver_linux64.zip, I think it did not pick up my http(s)_proxy environment variable.

@toymil
Copy link

toymil commented Nov 21, 2023

in the case of headless chrome what should I do

If chromium-driver is already installed from the system package manager, wasm-pack doesn't seems to need to download its own chromedriver.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants