From 4addc449f94a7e7598b383c70b73d1891188a701 Mon Sep 17 00:00:00 2001 From: Ole Fredrik Lie Date: Tue, 10 Oct 2017 12:37:22 +0200 Subject: [PATCH] Add info about static asset hashing in readme --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 311f34577..c4b2bcade 100644 --- a/README.md +++ b/README.md @@ -41,6 +41,9 @@ At the start of the build process a check is done to see if a `config.yml` file #### Browsersync setup If you want to take advantage of [Browsersync](https://www.browsersync.io/) (automatic browser refresh when a file is saved), simply open your `config.yml` file after creating it in the previous step, and put your local dev-server address and port (e.g http://localhost:8888) in the `url` property under the `BROWSERSYNC` object. +#### Static asset hashing / cache breaker +If you want to make sure your users see the latest changes after re-deploying your theme, you can enable static asset hashing. In your `gulpfile.babel.js`, set ``const REVISIONING = true;``. Hashing will work on the ``npm run build`` and ``npm run dev`` commands. It will not be applied on the start command with browsersync. This is by design. Hashing will only change if there are actual changes in the files. + ### 3. Get started ```bash