Not loading image processed by webpack correctly about django-webpack-loader HOT 7 CLOSED

No, feel free to open a PR addressing this or discussing solutions here.

from django-webpack-loader.

This is the expected behavior. From docs:

Please note that this approach will use the original asset file, and not a post-processed one from the Webpack pipeline, in case that file had gone through such flow (i.e.: You've imported an image on the React side and used it there, the file used within the React components will probably have a hash string on its name, etc. This processed file will be different than the one you'll grab with webpack_static).

To solve this for your use case, you need to drop the hash on your assetModuleFilename, that's what webpack docs suggest: https://webpack.js.org/guides/asset-modules/#custom-output-filename.

So change assetModuleFilename from "images/[name].[contenthash][ext]", to "images/[name].[ext]",

I'll keep this one open and close the other duplicate issues.
Sorry for this, but we don't have a solution that supports hashes yet.

from django-webpack-loader.

Hey fellow developers any update on the subject ?

from django-webpack-loader.

I'll let you know once I'll figure out something. Thanks for your reactivity btw

from django-webpack-loader.

Hello everyone

I suggest the following approach for adressing this issue with Webpack 5:

1. Add original source file paths of asset resources to webpack-stats.json
   django-webpack/webpack-bundle-tracker#125
2. Create the webpack_asset template tag that handles transformed files URLs
   #397

@fjsj What do you think?

from django-webpack-loader.

Thanks for the contribution @batistadasilva !
I'm excited to merge this, but please check PR comments.

from django-webpack-loader.

@fjsj Thanks for the review!

from django-webpack-loader.