I am not sure where Jocly gets the name from that it displays. One would indeed assume that it is from the *-config.js files, as these files must serve some purpose. (They are created on compilation of the source files, from data that is in the index.js file of the 'module' they belong in.)
Which cache did you clear? Your browser's, or CloudFlare? For Jocly the normal method of clearing the browser cache (Shift + load) does not work. I guess this is because the browser then only refetches the files linked to directly from the main HTML document. Jocly seems to fetch the variant-specific .js files only on command of the JavaScript in the 'core' files, once that starts running afterwards. Surfing to the changed .js file, and reloading that explicitly, should bring the latest version at CloudFlare into the browser cache, so Jocly would then use that if you restart it. (And it would allow you to directly check if the intended changes are indeed present.) Adding a ?nocache=true suffix when loading the changed .js file does not help, as the browser would consider that a different file than the one without the suffix (which is the one Jocly would use), and keep both cached.
BTW, there are still many occurrences of Malett with a single 'l' in the *-config.js file. I am not sure whether that will hurt. Some of the info in this file seems unused.
I am not sure where Jocly gets the name from that it displays. One would indeed assume that it is from the *-config.js files, as these files must serve some purpose. (They are created on compilation of the source files, from data that is in the index.js file of the 'module' they belong in.)
Which cache did you clear? Your browser's, or CloudFlare? For Jocly the normal method of clearing the browser cache (Shift + load) does not work. I guess this is because the browser then only refetches the files linked to directly from the main HTML document. Jocly seems to fetch the variant-specific .js files only on command of the JavaScript in the 'core' files, once that starts running afterwards. Surfing to the changed .js file, and reloading that explicitly, should bring the latest version at CloudFlare into the browser cache, so Jocly would then use that if you restart it. (And it would allow you to directly check if the intended changes are indeed present.) Adding a ?nocache=true suffix when loading the changed .js file does not help, as the browser would consider that a different file than the one without the suffix (which is the one Jocly would use), and keep both cached.
BTW, there are still many occurrences of Malett with a single 'l' in the *-config.js file. I am not sure whether that will hurt. Some of the info in this file seems unused.