asset/resource hash in name about file-loader HOT 12 CLOSED

You should not use file-loader with asset/resource, you don't need this loader with webpack anymore

from file-loader.

I will update docs in near future

from file-loader.

@alexander-akait but if I don't use file-loader for images then my webpack don't know where to look for images. even if I add alias and have image path ~assets/images/cat.png then browser keeps looking at localhost:8080/assets/css/~assets/images/cat.png (image defined in DOM) or localhost:8080/assets/images/cat.png (image defined in CSS). I have defined public path to /.

Alias definition:

resolve: {
    alias: {
      assets: path.resolve(__dirname, 'src/assets'),
    },
 }

so, do you have any suggestions how to load images successfully without file-loader, image name is hashed and then webpack can match path with hashed one?

from file-loader.

Expected, webpack@5 use publicPath: 'auto' by default and you don't need provide public path (if you don't use CDN)

I don't understand your problem, please clarify, don't use ~

from file-loader.

If you followed the issue template and filled in all the fields, you would get an answer and a solution long ago, I want to show for the future how formal things is help to other developers

from file-loader.

Custom output path https://webpack.js.org/guides/asset-modules/#custom-output-filename (same like outputPath), you don't need publicPath here

from file-loader.

from file-loader.

@alexander-akait
Hello, I still don't understand one thing, please tell me.

DEPREACTED for v5: please consider migrating to asset modules.

I have replaced file loader with asset modules, but I can't find how to set publicPath in asset modules.

Expected, webpack@5 use publicPath: 'auto' by default and you don't need provide public path (if you don't use CDN)

You said that in webpack@5, don't need to set publicPath if not using a CDN.
So what should I do if I use a CDN? Continue to use file loader?

In other words, is the following configuration equal before and after migration?

Use file loader:

module.exports = {
  test: /\.(png|jpg|gif|ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
  loader: "file-loader",
  options: {
    name: "[name].[contenthash].[ext]",
    outputPath: "img",
    publicPath: "/img",
  }
};

Use asset modules:

module.exports = {
  ...
  output: {
    path: distPath,
    filename: (chunkData) => {
      if (chunkData.chunk.name === entryName.devtools) {
        // Only used in local and development which no cache header
        return "assets/[name].js";
      }
      return "assets/[name].[contenthash].js";
    }
  },
  module: {
    rules: [
      {
        test: /\.(png|jpg|gif|ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
        type: 'asset/resource',
        generator: {
         filename: 'img/[name].[contenthash].[ext]'
       }
      }
    ]
  }
};

I set publicPath:"/img" when using the file loader, will using webpack default settings after migrating to the asset module have any other impact? Are you sure it's okay not to set publicPath here?

The images in the current project are displayed normally. But path like https://example.com/assets/... /img/demo.79e0ee9763e097c6d113.svg looks like an odd path URL.

from file-loader.

Why do you need CDN publicPath only for assets?

from file-loader.

@alexander-akait
Currently there is no such need, just saw you mention "if you don't use CDN", curious to ask.

So in webpack5, things like https://example.com/assets/... /img/demo.79e0ee9763e097c6d113.svg will not have side effects, right? It can be parsed correctly by any browser.

from file-loader.

Yes, but why you need /../?

from file-loader.

@alexander-akait
This is exactly why I said the URL address is strange. I always thought this was the behavior of Webpack@5, configured as follows.

module.exports = {
  ...
  output: {
    path: distPath,
    filename: (chunkData) => {
      if (chunkData.chunk.name === entryName.devtools) {
        // Only used in local and development which no cache header
        return "assets/[name].js";
      }
      return "assets/[name].[contenthash].js";
    }
  },
  module: {
    rules: [
      {
        test: /\.(png|jpg|gif|ttf|eot|svg|woff(2)?)(\?[a-z0-9=&.]+)?$/,
        type: 'asset/resource',
        generator: {
         filename: 'img/[name].[contenthash].[ext]'
       }
      }
    ]
  }
};

Does it look like it's to make the img and asset directories the same level?

from file-loader.