switch to ClientRequest so we have better control

[craig-day]

This PR switches from the isomorphic-fetch library to the native http and https modules to give us more control over request configuration.

The fetch library operates under the assumption its in the browser which means it doesn't allow certain headers to be set like Host, Cookie or User-Agent. Since this is an electron app, we don't have the same limitations.

I believe this PR will also resolve #112 and close #62

/cc @skevy @gjtorikian

[craig-day]

fyi @ThisIsMissEm and @rmosolgo I believe this resolves your issues

[gjtorikian]

nice

[gjtorikian]

With this change, I'm suddenly seeing an error:

Protocol "https:" not supported. Expected "http:"

Could you verify that? This was just from making a simple query to https://api.github.com/graphql.

[ThisIsMissEm]

I don't have time to test this, but the description sounds correct & like it'd fix the issue.

[craig-day]

Ah @gjtorikian yeah looks like thats a problem. Turns out its because I'm using the ClientRequest from the http library, and not the one linked in the README from the electron API. Now I have to figure out how to get electrons net object into the react app.

I would reach out to window and do const { net } = window.require('electron') but that feels messy.

[craig-day]

alright @gjtorikian after some digging, I got both http and https requests working, and I brought back the error handling that I unintentionally removed.

[gjtorikian]

Great, thank you! Release forthcoming.

[craig-day]

awesome. Thanks for the quick turnaround!