Skip to content

ESB64 v1.2.0 — espack merge architecture (attach accelerator by name)

Choose a tag to compare

View all tags
@thelabcorner thelabcorner released this 10 Aug 19:22
· 5 commits to master since this release
v1.2.0
a5955a0

ESB64 v1.2.0

New in this release

  • espack merge architecture (espack v0.3.0): ESPAK.attach now targets the accelerator by name ("ESB64Native") instead of the default index 0 — index is not a stable API under a merged bundle. The empty-payload short-circuit keeps the standalone accel-only bundle loading exactly as before.
  • ESB64.accel.jsx rebuilt on the espack v0.3.0 loader: shared-accel discovery for accel-less bundles (embedded-accel failure falls back to the on-disk shared accel), same WHATWG-exact native lane.
  • ESB64 stays the standalone shared "1" in the 1 + n model by design — no manifest/facade artifacts (its DLL is the accel embedded in every payload bundle, e.g. ESON/ESARR).

Assets

  • ESB64.accel.jsx / ESB64.accel.min.jsx — self-extracting accelerator bundle
  • ESB64Native.dll — freestanding WHATWG-exact accelerator (9,728 B), for embedding in your own espack bundle
  • ESB64.jsx, vendor-esb64.js, vendor-esb64-runtime.js, esb64-core.esm.mjs — facade/vendor/ESM builds

Validation

411 checks passed (WHATWG differential battery + vendored-runtime parity).

Assets 9
Loading