Different approach to require to avoid webpack bundling

[garyb]

This actually resolve #6 at last. Going via module.require worked in Affjax, so I've taken the same approach here.

@hdgarrood @jplatte do you know if there's a reason why we can't use module.require instead of require? Going via module should still work in node 6, should it not?

[garyb]

/cc @hdgarrood not sure if you'll get the ping above because I misspelled your name yet again before editing the correct speeelng in.

[jplatte]

I don't even know the difference. I just used require because that's what the example in the node documentation used. module.require does work on node 6.

[garyb]

Ok, thanks for testing! This should be fine then I think.

[garyb]

@jplatte There's nothing wrong with require usually, by the way. I'm attempting to intentionally prevent tools like Browserify and Webpack from treating it the way they're designed to do so in this case, as we don't want to bundle the node library code when in the browser.

[hdgarrood]

Looks sensible enough to me.