Add note about JSX usage about file-loader HOT 5 CLOSED

Ah thank god I found this. I agree it would be great to change the title of the issue for future people who are banging their heads against this.
I was searching for things like "broken images webpack" and "broken images file-loader".
Hopefully these breadcrumbs will lead people here...

from file-loader.

@oieduardorabelo known issue, should be fixed after #183

from file-loader.

@kswope
I had the same issue. I'm using ts-loader, though. It would be great if title of this issue was more to the point. For example: "require () creates two files instead of one". Then, I would have a chance to find this answer knowingly, and not like it is right now, by accident.

Thanks for Sharing, though. :)

from file-loader.

Anyone wants to update the readme with PR?

from file-loader.

I was having this problem today and, downgrading to file-loader": "0.11.2", worked as expected for me.

"babel-core": "6.26.0",
"babel-loader": "7.1.2",
"babel-preset-react-app": "3.0.2",
"file-loader": "0.11.2" // using 1.0.0, doesn't work 

in my case, I was importing the file in the top:

import IntroImage from '../../images/[email protected]';
import Slide0Image from '../../images/[email protected]';

... code

<img src={IntroImage} />

... etc

Using 1.0.0, the image was corrupted (in the webpack logs, we could see it being emitted, but, opening it via browser didn't work)

I managed to isolate the scenario in this repo: https://github.com/oieduardorabelo/file-loader-error

from file-loader.