Asset versioning

[haydenbleasel]

See: RealFaviconGenerator/gulp-real-favicon#5

• Timestamp
• File Hash (https://nodejs.org/api/crypto.html#crypto_crypto_createhash_algorithm)

Refer to RFG API for implementation style.

[strarsis]

So those links to extra gulp plugins indicate that URL-based cache busting
is rather the job of a different/extra plugin (I agree btw)?

With best regards

[haydenbleasel]

@strarsis I wish it could be, but since Favicons generates HTML and files but only returns files to the stream, only the files will get versioned if we use a seperate gulp plugin i.e. The HTML links will be incorrect.

[strarsis]

Also, for example, I would like to just include the generated HTML in a Jade layout template:

include ./generated/favicon.html

Can favicons also generate the necessary markup from scratch without a template index.html?
It seems to expect an existing HTML file, when I omit the option, no html is generated that I could include.

IMHO the generated HTML should just be that - minimal without things like hashes.
Then it can be postprocessed using another gulp plugin like gulp-rev-append.
Also, the HTML could be injected into the stream, too, a filter step can then be used to select either the image files or the HTML file using gulp-filter.

[haydenbleasel]

@strarsis Actually that's a good idea. Post favicons generation, you can use something like gulp-useref + gulp-rev + gulp-rev-replace to sort this stuff out. I've done something similar in Catalyst if that helps. Nice work.