Make reqwest client/server agnostic

[appsforartists]

Right now, trying to use reqwest from Node results in this error:

> var reqwest = require("reqwest")
ReferenceError: window is not defined
    at ./node_modules/reqwest/reqwest.js:13:13
    at win (./node_modules/reqwest/reqwest.js:8:72)
    at Object.<anonymous> (./node_modules/reqwest/reqwest.js:11:2)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:349:32)
    at Function.Module._load (module.js:305:12)
    at Module.require (module.js:357:17)
    at require (module.js:373:17)
    at repl:1:15

Given that there are projects to provide the XHR interface in Node, making reqwest isomorphic should be as simple as abstracting out the implicit use of globals like window and document.

[appsforartists]

Started working on it here:

https://github.com/appsforartists/reqwest

[alexaivars]

+1

[markbahnman]

Ran into this same issue when prerendering a react page that used reqwest, being able to be used in node would be a huge plus.

[appsforartists]

@markbahnman The fork I linked above has been working for me.

[ded]

@appsforartists @alexaivars @markbahnman
this is an interesting issue given I've always used request within Node since it solves a plethora of other problems. Given Node and the browser are two completely different beasts, it would bloat this library to no end. Therefore, when I'm working on the frontend, I use reqwest, and when in node, I use request.

Go ahead and look at the source for https://github.com/mikeal/request and you'll see it solves a number of other problems that this library doesn't even attempt to address. And visa/versa.

[appsforartists]

@ded I haven't looked through request much, but if xhr2 continues to work as-advertised, that should polyfill all you need to worry about for the HTTP layer in Node. Then, it's just a matter of being careful about not-presuming that browser properties are global. As you can see, the footprint of appsforartists@796d511 is pretty damn small.

It's your library. You've spent a lot of more time than I have thinking about these things, and I'm certainly not going to tell you what to support, but are you amenable to something like appsforartists@796d511 to enable reqwest to be used in isomorphic apps (if the node-implementation can be offloaded to a polyfill like xhr2)?

The apps I'm working on nowadays use identical code on the client and server, so using two different libraries for data is really unappealing. If we could make reqwest isomorphic without bloating or wholesale rewriting, that would be awesome!

---

Also interesting to note, @mjackson's mach is aiming to be the end-all http library for JS, equally adept at the client and server. However, I don't think the client story has been fleshed out yet.

[blainekasten]

+1 for agnosticism. (in this context)

[raysuelzer]

+1 right now, I can't use the library with reactjs,net without a hassle.

[raysuelzer]

@appsforartists could you put in a pull request for this issue? Isomorphic apps are becoming more and more popular, so being able to include this dependency in webpack is pretty important. I don't want to have to hack together two different versions of my javascript more than I need to.

[appsforartists]

@raysuelzer sure. FWIW, I use mach now, which is agnostic. If you're feeling future-proof, there's also fetch.

[appsforartists]

@raysuelzer I don't know if @ded is interested, but there's now a PR open at #185.

[blainekasten]

@appsforartists thanks for doing that! Hopefully @ded is interested.

[luandro]

+1 for reqwest in isomorphic apps

[yicone]

+1 for reqwest in isomorphic apps