Builds a UMD file for the browser when publishing.

[qubyte]

This PR coaxes browserify into making a standalone build. This allows the built file to be used in AMD environments as well as a browser global.

@paulmelnikow This is an alternative to #5.

[paulmelnikow]

Neat approach!

I rebased my tests on this version and updated them to require the pre-built file. The webpack build works correctly but generates this warning:

WARNING in ./build/fetch-browser.js
Critical dependencies:
1:486-493 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./build/fetch-browser.js 1:486-493

The browserify build works fine, and makes no complaint.

A slight disadvantage to this approach is that whatwg-fetch gets pulled in as a string literal and can't be minified.

To try to dodge this warning, do you think it would be worth shipping the CommonJS and UMD builds separately?

Here's the branch with the tests: https://github.com/paulmelnikow/fetch-ponyfill/tree/test_umd_version

[paulmelnikow]

For require('fetch-ponyfill')() to work from Node, node-fetch needs to stay in dependencies.

[qubyte]

Whoops, good catch.

[qubyte]

I have an idea on how to make this leaner. It means ditching browserify and making a hand rolled builder. I'd rather not separate UMD stuff where possible, but hand rolling can make it a lot smaller. I'll experiment...

[qubyte]

@paulmelnikow Take a look now. There's still a bit of module fluff in there, but the rest is minifier friendly. It's pretty hacktastic, but then so was the original.

[qubyte]

It also fixes an issue of the existing version not working in a web worker without manually passing in config.

[paulmelnikow]

Builds clean, and minifies! I like it. 👍

When you publish, it looks like fetch-browser.js and build.js will be included, while build/fetch-browser.js will not.

You can either use .npmignore or the files argument. I think the second is probably cleaner:

"files": [
  "fetch-node.js",
  "build/fetch-browser.js"
],

That seems to be the right incantation. You can use npm pack or pkgfiles to test what you're getting.

[qubyte]

Odd. That should have worked. In any case, including the files list is a good idea (less stuff in the tar ball). Nice catch! I'll update.

[qubyte]

Added and checked, seems to be working.

[paulmelnikow]

Looks good!

[paulmelnikow]

Stoked!

Would you mind doing an npm release so I can try to integrate it?

[qubyte]

No problem. I'll bump the whatwg-fetch version and release it.

[qubyte]

Released as v1.0.0 (tracking whatwg version).

[paulmelnikow]

We started integrating this today, and it's working great!