Bower proxy setup

is there a way to configure bower not only to use a proxy server, but also to ignore the proxy server configuration for some domains?

I have a problem: I will run the internal registry for our own developed components. For this repository, I would like to ignore the proxy configuration.

+50
bower proxy
Aug 21 '13 at 14:15
source share
11 answers

For information, you can add the no-proxy attribute in your .bowerrc file. I do not know since when it is supported, but it works on bower 1.7.4

.bowerrc:

{ "directory": "bower_components", "proxy": "http://yourProxy:yourPort", "https-proxy":"http://yourProxy:yourPort", "no-proxy":"myserver.mydomain.com" } 

Hello

+42
Mar 02 '16 at 14:16
source share

Modify the .bowerrc file (should be next to the bower.json file) and add the desired proxy configuration

 "proxy":"http://<host>:<port>", "https-proxy":"http://<host>:<port>" 
+76
Jan 23 '14 at 8:17
source share

I had an ETIMEDOUT error, and after posting

 { "proxy":"http://<user>:<password>@<host>:<port>", "https-proxy":"http://<user>:<password>@<host>:<port>" } 

just worked. I don’t know if you have something wrong in .bowerrc or ECONNRESET, this cannot be solved, but I hope this helps you;)

+25
Mar 03 '14 at 12:02
source share

I struggled with this because of the proxy server, so I decided that I should publish what I did. The below one works for me.

-> "export HTTPS_PROXY = (yourproxy)"

+14
Mar 13 '14 at 12:36
source share

It is not possible to configure an exception for the proxy server settings, but my colleague had a solution to solve this specific problem. He installed a local proxy called cntlm . This server supports ntlm authentication and exceptions for general proxy settings. Perfect match.

+7
Sep 05 '13 at 13:12
source share

The key for me was to add an additional string "strict-ssl": false

Create .bowerrc in the root folder and add the following,

 { "directory": "bower_components", // If you change this, your folder named will change within dependecies. EX) Vendors instead of bower_components. "proxy": "http://yourProxy:yourPort", "https-proxy":"http://yourProxy:yourPort", "strict-ssl": false } 

Good luck to the people who still stick to this.

+6
Dec 27 '15 at 21:13
source share

Inside the local project, open a .bowerrc file containing:

 { "directory": "bower_components" } 

and add the following line of code:

 { "directory": "bower_components", "proxy": "http://yourProxy:yourPort", "https-proxy":"http://yourProxy:yourPort" } 

version for bowling: 1.7.1

Greetings

+4
Dec 15 '15 at 20:13
source share

Add the following entry to your .bowerrc :

 { "proxy":"http://<user>:<password>@<host>:<port>", "https-proxy":"http://<user>:<password>@<host>:<port>" } 

Also, if your password contains any special character encoding a URL, For example: replace the @ character with% 40

+1
Apr 21 '16 at 13:47
source share

create a .bowerrc file in your home directory and add it to the file that worked for me

{

  "directory": "bower_components", "proxy": "http://youProxy:yourPort", "https-proxy":"http://yourProxy:yourPort" } 
0
Mar 18 '16 at 20:10
source share

Are you using windows? Just set the http_proxy environment variable ...

 set http_proxy=http://your-proxy-address.com:port 

... and the conversation will take it. Instead of dealing with a unique configuration file in a project folder - right? (side-note: when-the-F! windows will allow us to create a .file using explorer? c'mon windows!)

0
May 05 '17 at 9:14 p.m.
source share

add .bowerrc

 {SET HTTP_PROXY= http://HOST:PORT,SET HTTPS_PROXY=http://HOST:PORT} 

In NPM, you must do the following in the console:

 npm --proxy http://Host:Port install 
-5
Nov 20 '15 at 19:06
source share



All Articles