Skip to content
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.

bazel run @yarn//:yarn not work with or without proxy #91

Closed
mapx opened this issue Feb 18, 2018 · 3 comments
Closed

bazel run @yarn//:yarn not work with or without proxy #91

mapx opened this issue Feb 18, 2018 · 3 comments

Comments

@mapx
Copy link

mapx commented Feb 18, 2018

If some packages are not accessible without proxy, one might try:

$ https_proxy=http://myproxy.at:1234 bazel run @yarn//:yarn

It works fine until $ concurrently "webdriver-manager update" "ngc -p angular.tsconfig.json" and ends up with angular/webdriver-manager#239

Is there some way to pass the proxy information to webdriver-manager?

@alexeagle
Copy link
Contributor

I think you'd need to split up the package.json something like

scripts: {
  "webdriver-manager": "https_proxy=http://myproxy.at:1234 webdriver-manager update",
  "ngc-angular": "ngc -p angular.tsconfig.json",
  "postinstall": "webdriver-manager && ngc-angular"
}

@mapx
Copy link
Author

mapx commented Feb 20, 2018

Thanks :)
Sometimes the proxy is introduced and removed in different environments. It would be nice if the configuration stays outside of source files.

@alexeagle
Copy link
Contributor

You'd have the same issue without Bazel / ABC - this is a consequence of using webdriver in your environment. I don't think there's anything I can do to improve it.

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

No branches or pull requests

2 participants