arantes555

What makes you believe that a fetch to https://www.google.com should actually return a 307 redirect ? When trying with curl, it actually returns a 200 for me, so I am...

@jkpadmanapan I can confirm that I also get a 200 with http ``` ➜ ~ curl http://www.google.com -I HTTP/1.1 200 OK Content-Type: text/html; charset=ISO-8859-1 P3P: CP="This is not a P3P...

Sorry for earlier. You are right, the `redirect` option does not work when running on Electron. It works when `electron-fetch` is running in node, but not on electron. It's actually...

Thank you for the PR ! This would be a breaking change, and in my opinion is not big enough to warrant a major version bump. I will keep this...

I have to admit, I have not had to use client certificates in a *long* time, and never in electron, but a quick search gave me this : https://electronjs.org/docs/api/app#event-select-client-certificate It...

This is quite surprising, from what you are saying it looks like an Electron bug. According to the docs (https://www.electronjs.org/docs/latest/api/client-request/#event-login) the `req.on('login')` is supposed to be "emitted when an authenticating...

Just ran into the same issue today... Had to work around it by putting a `postinstall` script that does ```javascript const fs = require('fs') const toRemove = '&& !folderName.startsWith("@")' const...

Any progress on this? It's IMO the one thing missing for this extension to be perfect!

Thanks for your answer. I just thought that the major version bump was to deal with all the minor inconsistencies that might exist between `sass` and `node-sass`, not the `/deep/`...

Seeing the same problem here... setting `mangle: false` in the options seems to work-around the problem.