Use a dedicated file for storing extension info

Chrome has getManifest(), Safari doesn't have anything, Firefox has an
asynchronous API...
So, instead of using extension APIs, store the common informations
(extension name, version, homepage url) in a file (vapi-appinfo.js), which
can be included when it's needed (its data will be available at vAPI.app.____).
The file's content is updated each time the extension is being built, so
it shouldn't be modified manually.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/js/assets.js b/src/js/assets.js
index 80dc0fe..6d8164b 100644
--- a/src/js/assets.js
+++ b/src/js/assets.js
@@ -97,7 +97,7 @@ var cachedAssetsManager = (function() {
         // Flush cached non-user assets if these are from a prior version.
         // https://github.com/gorhill/httpswitchboard/issues/212
         var onLastVersionRead = function(store) {
-            var currentVersion = µBlock.version;
+            var currentVersion = vAPI.app.version;
             var lastVersion = store.extensionLastVersion || '0.0.0.0';
             if ( currentVersion !== lastVersion ) {
                 vAPI.storage.set({ 'extensionLastVersion': currentVersion });