Roadmap discussion for 3.0

Plans for v3.0.0 (updated as discussion progresses)

• 1. drop old IE support, keep it in require('xhr/legacy') or just let people use 2.x
• 2. ensure all options that xhr implements are compatible with request
• 3. add fully automated cross-browser tests (surprisingly hard to do if you need to have a mock server)
• 4. stop accepting content in json option, make it boolean
• 5. fix #149

If you have any other important items on your agenda and want to start/keep contributing to xhr feel free to chime in.

[dhritzkiv]

Another: Remove some dependencies that are overkill. Namely xtend and is-function

xtend is used in one place:

//L39...
else {
    params = xtend(options, {uri: uri})
}
//...

Where this can simply be achieved with:

//L39...
else {
    params = options;
    params.uri = uri;
}
//...

And is-function, since typeof options === "function" is enough of a check, especially in the browsers that v3.0 will support.

[naugtur]

@reqshark we’d drop most of the support for browsers that don’t have a standard compliant XMLHttpRequest object, so in IE8 and IE9 cross-origin will no longer work. Also, tweaks for IE8 will go away. New version should be usable (with some hacks) on IE9 for very basic things.

@TehShrike @mhart I think you’re both right 😃 We should be able to figure out what the breaking changes will be and focus on releasing the breaking changes as 3.0 and then work on non-breaking changes for 3.1, 3.2 … It’d be a bad thing for our userbase if we quickly released v3, v4 and so on.

Anyway, I think we should focus on figuring out how to run cross-browser tests of the whole thing, because every new service for running browser tests I found would not let us make requests outside or start a node server. It was only possible with (now deceased) Testling. I’ve been testing on localhost with browsers on VMs ever since.