Document how to use in Browserify…

[matthew-andrews]

… as per #21. This is just a quick first pass, I'm almost certainly using too many words here.

• I've proposed changing the suggest ES6 Promise implementation to native-promise-only as I believe its API is more similar to the CommonJS API fetch has*. Would you like me to change that back?
• Would you like me to squash my commits?
• Is ‘fuzzy versions’ clear enough or should I change this to ‘version ranges’?

* The equivalent for es6-promise is:

require('es6-promise').polyfill(); // require('native-promise-only');

It would be nice if we can do #9 because it would simplify some of this explanation (around fuzzy versions/version ranges) greatly.

[josh]

It doesn't look like native-promise-only was packaged for npm, not bower.

[matthew-andrews]

crumbs, i'll put it back

[josh]

Ah, so native-promise-only doesn't require an explicit export when used in CJS mode.

I'd be cool recommending either. I guess thats the nice thing about it being optional is that you can use whatever promise polyfill you like.

[matthew-andrews]

Yeah, es6-shim is the same and appears to have bower support?

[I am completely subscribed to this point of view: https://github.com/matthew-andrews/denodeify]

[matthew-andrews]

Is this OK to merge or would you like to make any changes?

[josh]

It looks good to me @matthew-andrews.

I was waiting for @dgraham to review and merge.

[dgraham]

Thanks for writing this up!