ScriptVault v2.3.1
Fixes a broken v2.3.0 — extensions failed to load with Could not load icon 'icons/16.png' specified in 'icons' because the manifest referenced a directory that was deleted during v2.3.0's branding cleanup. Also fixes a separate ZIP-format issue: the v2.3.0 ZIP used Windows-style backslash entry names (images\icon128.png) which Chrome cannot match against manifest paths regardless of file presence.
Install (Brave / Chrome / Edge — recommended)
Dragdrop CRX installs are blocked by Chromium 75+ for any extension not in the Web Store, regardless of signing or developer mode. Use Load unpacked instead:
- Download
ScriptVault-v2.3.1.zipand extract it to a permanent folder (e.g.~/extensions/scriptvault/). Don't delete the folder afterwards — the browser loads the extension from this path on every startup. - Open
brave://extensions(orchrome://extensions,edge://extensions). - Toggle Developer mode on (top-right).
- Click Load unpacked and select the extracted folder.
The CRX is still attached for users who have a flow that supports it (enterprise policy with ExtensionInstallSources whitelist, Chrome --load-extension command-line flag, or older Chromium forks like Vivaldi). It is signed with a self-distribution key (extension ID dogogpmmlddegcodbcbeccebdlegphph) — distinct from the Chrome Web Store listing.
Changes
- Fixed:
manifest.jsonreferencedicons/16.png/icons/32.png/icons/48.png/icons/128.png, but theicons/directory was deleted in v2.3.0's branding cleanup. Repointed manifest,pages/popup.html,modules/public-api.js,modules/backup-scheduler.js, and the TypeScript mirror atsrc/modules/public-api.tsto the survivingimages/icon{16,32,48,128}.pngfiles. Firefox manifest was already correct. - Fixed:
build.sh/publish.shPowerShellCompress-Archivefallback wrote Windows-style backslash entries (images\icon128.png). Switched tobsdtar(C:\Windows\System32\tar.exe), which writes POSIX-style forward-slash entries that Chrome can match.
523/523 tests green.