Mikeal Rogers

We need to support this in Node.js as well.

Actually, I take that back, there’s isn’t much to do in Node.js. I’d like to avoid an API here that has to touch `core.js`. It shouldn’t even need to extend...

You shouldn’t need to pass the agent in. Node.js Core batches concurrent requests together to optimize for keep-alive. The browser does the same. You’d only need to manage your own...

You just pass them in as part of the URL path.

I’ve gone back and forth on this one. One one hand, i hate having to do write this over and over again, but I also can’t think of a great...

What do people think about this: 1. We allow you to pass an instance of `URLSearchParams` that will be **appended** to the URL (after concatenation if you’re using that feature...

It’s a little late to go changing the function signature. I’m actually quite fond of using destructuring this way, i do it a lot in other modules, but it’s a...

bent returns a stream by default, but unlike request it doesn’t instrument the pipe() command to set the method and headers on a subsequent http stream, so you’ll need to...

`bent` doesn’t implement redirect following, although I have considered adding it. But in the browser we use `fetch` which does its own redirect following, which is why it’s been a...

hrm... I try not to add any features that can’t be supported in the browser. But we should expose some kind of way to pass additional options to the underlying...