Not able to copy an image file about file-loader

[allisonwhilden]

I'm new to all of this, and I don't know if this helps at all -- but I ran into what seemed like a similar problem. When checking out my emitted image files, they appeared to be smaller in size and wouldn't open at all. I changed the extension of these files to .txt and opened them in a text editor, and noticed that they appeared to be a shortened data URI string -- but not the complete one you would get if you converted your original image to a data URI string.

Further investigation found that I appeared to have been running the files both through the URL-loader via my webpack config, and through file-loader in a similar 'require' statement in my CSS file. When I just used one or the other, everything worked out. So, if I commented out my URL-loader in my webpack config, my 'require' statement worked.

Don't know if this makes sense, is intentional, or is helpful at all -- I'm still very much learning all of this. But sharing it just in case it saves anyone else time.

[flyingzl]

Same +1

My workaround is : add exclude to webpack.config.js

            {
                test: /\.(png|jpg|gif)$/,
                exclude: /\.dp\.(png|jpg|gif)/,
                loader: "url",
                query: {
                    limit: 8192,
                    name: 'imgs/[name].[ext]'
                }
            },

Please pay attention to the exclude, if a image named with foo.dp.png, it will not be parsed by url-loader, and you can require or import the image like the following codes:

import icon from 'file-loader?name=imgs/[name].[ext]!./foo.dp.png';
console.log( icon ) // imgs/foo.dp.png

import bar from './bar.png'
console.log(bar) // data:image/png;base64,iVBORw0KGgoAAAANS.....

[Yankovsky]

Same problem

[DevilZh]

Same +1

[SpaceK33z]

You can't use the file-loader twice this way. What @flyingzl said is the best answer.