Static file asset revisioning through content hashing
npm install grunt-rev --save-dev
Once that's done, add this line to your project's Gruntfile:
If the plugin has been installed correctly, running
grunt --help at the command line should list the newly-installed plugin's task or tasks. In addition, the plugin should be listed in package.json as a
devDependency, which ensures that it will be installed whenever the
npm install command is run.
Use the rev task together with yeoman/grunt-usemin for cache busting of static files in your app. This allows them to be cached forever by the browser.
In your project's Gruntfile, add a section named
rev to the data object passed into
algorithm is dependent on the available algorithms supported by the version of OpenSSL on the platform. Examples are
'sha512', etc. On recent releases,
openssl list-message-digest-algorithms will display the available digest algorithms.
The number of characters of the file content hash to prefix the file name with.
This will rename
app.css with an 8 character long hash prefix. For example
css/ae35dd05.app.css. The hash value depends on the file contents.
Change the algorithm or length to style the generated asset file names. Note that the
usemin companion task requires at least one anycase hexadecimal character to prefix the file name.
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.