Properly hash images based on contents and allow skipping generation of images #826
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is for nuxt 2 and recognise it may too much trouble to have merged in, but i wanted to open the PR in case it was useful for the core package, or the wider community
I patched the code so that it actually hashes the image based on the contents, not the filename, as that is more useful.
And on top of that, I've also added a method to the options to allow for skipping generation for files, couple with the contents hashing mentioned above, this becomes a very powerful method to speeding up build times potentially
The npm package of the fork is here, if anyone needs to use this functionality in their application
https://www.npmjs.com/package/jthawme-nuxt-image