All committers have signed the CLA.

Aw, no fair on the decreased coverage - it's because there's fewer lines of code :-(

Maintainers - I can add tests to increase the coverage score, but that will increase the scope of these changes. What would you like me to do?

Hi!

We would love to see some feedback given on this issue so that it may be merged and released.
We're depending on it as part of our CRA react-scripts@0.10.0 release, which switches to webpack@2!
@pugnascotia has been working hard to give us a whitelisted url-loader and our comprehensive e2e uncovered this bug. 🔥

Let me know if there's anything I can do to help facilitate this process, and thanks to all parties!

/cc @jhnns

Thanks! That looks good. It makes sense to use path.parse() here since loaderContext.resourcePath is a native, absolute path, so node's parsing algorithm should work as expected. I don't know why @sokra preferred to parse it manually here 😬

Published as 1.0.3