Integrity can only be used if the physical files exist

[karolyi]

Hey,

I've turned on integrity and experienced errors so far with:

• using webpack-dev-server that only stores the files in-memory since they will get rebuilt upon change
• sourcemap files that aren't built or not in the place the bundle tracker thinks they are

Tracking this bug leads to

webpack-bundle-tracker/lib/index.js

Line 31 in 4596d47

return fs.readFileSync(path, { encoding: 'utf-8' });

where the readFileSync gets a path that doesn't exist and raises an exception that isn't handled.

This results in webpack silently hanging upon building the bundle with integrities.

Disclaimer: I'm not a webpack dev, just a guy who tries to use this plugin with django, emitting the integrity values in templates. If not otherwise solvable, unavailable integrity calculations should at least raise an error so guys like me would know what happened.

[karolyi]

I have something in the works for this. PR coming up.

[rvlb]

Integrity calculation has been revamped at #132, now we'll always use the content from the in-memory asset that webpack emits, which won't break with webpack-dev-server. An example with a similar setting has been updated on the django-webpack-loader side https://github.com/django-webpack/django-webpack-loader/blob/v3.2.2/examples/hot-reload/webpack.config.js.