No fingerprints assets - Netlify and cache busting urls

[igk1972]

This pull request adding the config option for disable the fingerprints in files. The files are obtained without changes.
PR no effective without PR #839

This is very necessary when the site has tens of thousands of HTML pages and as many json files.
Deployment time exceeds half an hour or more.

For support hosting like Netlify.
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/

Netlify processes every new file. It takes a lot of time.
Fingerprints are not needed for Netlify. The service runs on information in etag.
Also see gatsbyjs/gatsby#11961 (comment)

Probably not everyone needs this feature. But pull request allows now to solve the problem of deploying large sites on Netlify.

Gatsby has the same problems.
gatsbyjs/gatsby#11961

[hjvedvik]

Thanks! I can review your PRs tomorrow :)

[igk1972]

Related #584

[igk1972]

PR no effective without PR #839

[hjvedvik]

Thanks again for a good PR @igk1972 :) I have just one question. Can the option be urlFingerprints: false instead? We are trying to have a pattern for options where false will disable a default behavior.

[hjvedvik]

Or maybe cacheBusting: false because the JSON files actually have the hash inside the content instead of the URL. But it might not matter much :)

[igk1972]

It is not so important.

Make (change) an option at your discretion, as you consider it better.

[igk1972]

cacheBusting is good :)

[hjvedvik]

Okay, then rename it to cacheBusting which defaults to true for the current behavior :)

[igk1972]

I did as needed, added a commit

[hjvedvik]

Thank you @igk1972 :)

[hacknug]

@hjvedvik any chance we can get something like this working for pages too?