Use node ecosystem about fetch

[josh]

I get that node users prefer this flow, but what would be the benefit?

FWIW, browserify already works since its just a polyfill, not a module with any exported symbols.

[josh]

If anything, going in the opposite direction would be preferred to me.

We can remove the bower install dependency from the dev chain and just use curl to fetch down the polyfill scripts we're depending on. Or just check them in.

[josh]

How does the test tooling this repo uses affect you're actual application integration of the polyfill?

[josh]

Replace your shell script test runner with an environment that can run from within node

Maybe you're confused, this polyfill is for running in browser environments, not node. Which is why we want to test in PhantomJS.

[tracker1]

@josh

Honestly, my suggestions were mainly out of the fact that this is a JS project, that already needs node (for bower, phantom-js, your test environment, etc) and could, via some minor adjustments use that same environment without any need for additional tooling, and work cross platform. Windows and OSX don't have make and windows doesn't have bash without additional software... with minor adjustments you could remove those dependencies in favor of a node (already required) solution.

I'm now using browserify with most of my logic being the same for server (node) and client (browser) rendering, so tools that support both modes of operation and are published in npm are (imho) better than those that aren't. It also is a trend that is seeing a lot of growth.

[dgraham]

I'm going to close this out since it's working well so far. I appreciate the suggestion to use more node ecosystem tools, but we can rely on make being available. The development flow is pretty simple right now.