Skip to content

v0.3.1 — Chrome + TM bundle scoping fix

Choose a tag to compare

View all tags
@11sid11 11sid11 released this 01 Jul 12:10
v0.3.1
0f5c4da
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.3.1 — 2026-07-01

Critical bugfix for v0.3.0. The chrome extension and TM userscript from v0.3.0 were non-functional in browser due to two cumulative scoping bugs. Anyone who installed v0.3.0 should update.

Fixed

  • Chrome extension v0.3.0 was completely non-functional in browser. Crashed at loadChromeStorage is not defined on first load.
    • Two root causes (missing imports + wrong build order); both fixed.
  • Tampermonkey userscript v0.3.0 had the same scoping bug. Would also have been non-functional. Masked in the field because TM's auto-update prompts but does not force, so users on v0.2.2 kept working until they accepted v0.3.0.
    • Two mirror-image root causes; both fixed.

Notes

  • Regression tests added (test/chrome-bundle.test.js, test/tm-bundle.test.js) that load the built bundle in a vm context and assert window.__batchd is stamped without ReferenceError.
  • Build script now asserts the chrome bundle contains loadChromeStorage + chromeStorage strings (catches the missing-imports half at build time).

Install

  • Tampermonkey auto-updates from this URL.
  • Chrome Web Store update is in flight (zip already uploaded to CWS as of this release).

Full changelog: https://github.com/11sid11/Batchd/blob/v0.3.1/CHANGELOG.md

Assets 3
Loading