fix: properly handle webpack loaders

[ariporad]

Fixes #17.

[Pomax]

A possible test for this would be to have a file with something like:

var emptyTransform = function(source, filename) {
  return "module.exports = {};\n";
};

addHook(emptyTransform, ['text']);

require('file!something.text?name=thing.with.dot');

[Pomax]

hm, it looks like this won't work, as pirates kicks in after the base file consultation goes through, so node will try to get the file content, then hand it over to pirates, which will fail on webpack syntax.

There are ways around this (loader instructions in a webpack.config.js for instance) so I guess it might be a case of "document that this won't work, rather than fix"?

[ariporad]

@Pomax: Ok, I'll close this, would you mine submitting a PR to document it? You seem to know a good bit more about this than me.

[Pomax]

will do

[Pomax]

filed as #21