configureImageRule and configureFontRule [ext] is different from copyFiles

[Seb33300]

The filename option of configureImageRule and configureFontRule is not consistent with copyFiles.

With copyFiles, [ext] doesn't include the dot => jpg
With configureImageRule, [ext] includes the dot => .jpg

This means we have to set 2 different config to achieve the same result:

.configureImageRule({filename: '[path][name].[hash:8][ext]'})
.copyFiles([{context: './', from: './assets/images', to: '[path][name].[hash:8].[ext]'}])

[sacerro]

Hi,
I have the same issue. Is there any news on this? Maybe my config (similar to @Seb33300) is wrong?

.configureImageRule({
  type: 'asset',
  filename: `images/[name]${(Encore.isProduction() ? '.[hash:8]' : '')}[ext]`,
})

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[Kocal]

Hi, this issue is coming from Webpack itself, .copyFiles() is based on file-loader and uses .[ext] (see https://v4.webpack.js.org/loaders/file-loader/#string).

Since this loader is deprecated in Webpack 5, it maybe a good idea to migrate this feature to https://webpack.js.org/guides/asset-modules/ or https://github.com/webpack-contrib/copy-webpack-plugin instead.

[Lyrkan]

Hi, this issue is coming from Webpack itself, .copyFiles() is based on file-loader and uses .[ext] (see https://v4.webpack.js.org/loaders/file-loader/#string).

Since this loader is deprecated in Webpack 5, it maybe a good idea to migrate this feature to https://webpack.js.org/guides/asset-modules/ or https://github.com/webpack-contrib/copy-webpack-plugin instead.

Hey @Kocal,

FYI when implementing the .copyFiles()` method I initially tried to use the copy-webpack-plugin but there were a few issues related to the generation of the manifest file. You can find more details here, not sure if that's still relevant.

As for using asset modules... I think I tried doing it after updating to Webpack 5 but can't remember why it did not happen.

[Kocal]

@Lyrkan !! :D
It's been so long, I hope you are going well!

Thanks for the explanations, they're super valuable here.

[carsonbot]

Thank you for this issue.
There has not been a lot of activity here for a while. Has this been resolved?

[carsonbot]

Could I get a reply or should I close this?

[carsonbot]

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!