When I have a loader configuration with multiple tests matching a file, I would expect only the first matching loader to be used but that doesn\'t seem to be the case.
This answer was helpful to me but I'd like to complement with another point which affects loader order, which is the loadername! approach.
Let's say you have an url-loader in your config with an higher priority than file-loader and you'd like to import an image path with the latter. Doing nothing would import the file via url-loader (which creates an encoded data-url).
Prefixing the import with file-loader! would direct the import to that loader.
import image from 'file-loader!./my-img.png'