Generated meta file should be named meta.json

Author: flexdinesh

README.md

@@ -9,7 +9,7 @@ There are different approaches that work for different types of websites. I rece
 - We want the site to load from the cache if there is no new version
 - We want to refresh the cache every time a new version of the app is deployed
 - We use npm package versioning to version our app and each deploy will be versioned incrementally
-- We build a `meta.json` file along with every build and it will act as a REST endpoint (won't be cached in browser)
+- We generate a `meta.json` file along with every build in the public dir and it will act as a REST endpoint (won't be cached in browser)
 - We refresh cache (`window.location.reload(true)`) in the browser whenever a new version is released
 
 ## License

generate-build-version.js

@@ -5,18 +5,18 @@ const packageJson = require('./package.json');
 const appVersion = packageJson.version;
 
 const jsonData = {
-  appVersion: appVersion
+  version: appVersion
 };
 
 var jsonContent = JSON.stringify(jsonData);
 
-fs.writeFile('./public/version.json', jsonContent, 'utf8', function(err) {
+fs.writeFile('./public/meta.json', jsonContent, 'utf8', function(err) {
   if (err) {
-    console.log('An error occured while writing JSON Object to version.json');
+    console.log('An error occured while writing JSON Object to meta.json');
     return console.log(err);
   }
 
-  console.log('version.json file has been saved with latest version number');
+  console.log('meta.json file has been saved with latest version number');
 });
 
 /* eslint-enable */

package.json

@@ -1,6 +1,6 @@
 {
   "name": "cache-busting-example",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "private": true,
   "repository": {
     "type": "git",

public/meta.json

@@ -1,3 +1 @@
-{
-  "version": "0.0.1"
-}
+{"version":"0.1.1"}