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

[mapx]

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]

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]

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

[alexeagle]

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.