three-slicer 0.4.2 → 0.4.3

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## 0.4.3 — 2026-11-07
+
+Performance work measured in Firefox and Chromium, and the changes that let the browser extension be listed on
+Firefox Add-ons (AMO).
+
+### Changed
+
+- The single-threaded kernel ships its wasm as a file, `engine/src/slicer_core.wasm`, as the threaded one already did.
+  Inlined, the glue was a 7.2MB script, and AMO's validator refuses any JS file over 5MB; it is 85KB now. Vite and
+  webpack emit the wasm as an asset. A host that serves the package files itself has to serve this file as
+  `application/wasm` too, and from another origin with `Cross-Origin-Resource-Policy: cross-origin`. G-code is
+  byte-identical to the inlined build.
+- A plate's toolpaths are skipped when the plate is off screen. Zoomed onto one of 28 sliced plates (Hylian Shield,
+  M5 Pro, DPR 2), GPU time per frame went from 16.0 to 1.4 ms in Chromium and from 17.8 to 2.1 ms in Firefox. The
+  whole-bed view is unchanged at about 14 ms.
+- Hover, the paint brush and Measure pick through a per-mesh grid instead of testing every facet. Hover picks at most
+  once per frame and not while a button is held, so an orbit or a drag no longer raycasts the scene.
+- Slice progress and the plate tabs' run state re-render once per frame, however many pool workers report.
+
+### Added
+
+- `npm run pack:firefox` in `web/extension` builds the zip for an AMO upload.
+
 ## 0.4.2 — 2026-11-03
 
 ### Added

package/README.md

@@ -705,7 +705,7 @@ Without those headers, the engine falls back to the single-threaded kernel.
 The multithreaded kernel's wasm is a file beside its glue, `engine/src/slicer_core.mt.wasm`, reached through
 `new URL('slicer_core.mt.wasm', import.meta.url)`; Vite and webpack emit it as an asset. Serve it as
 `application/wasm`, and from another origin (a CDN) with `Cross-Origin-Resource-Policy: cross-origin`, or the
-cross-origin isolated page cannot load it. The single-threaded kernel still inlines its wasm.
+cross-origin isolated page cannot load it. The single-threaded kernel does the same with `engine/src/slicer_core.wasm`.
 
 ## Data Files
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "three-slicer",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "Browser/WASM 3D-printing slicer reverse-engineered from OrcaSlicer: slicing engine (Arachne walls, tree/grid supports, multi-material), SLA resin slicing with PrusaSlicer's ported support/pad chain and .sl1 export, React viewer with GPU toolpath preview, and schema-driven settings UI.",
   "license": "AGPL-3.0-or-later",
   "type": "module",
@@ -96,6 +96,6 @@
     "clipping"
   ],
   "dependencies": {
-    "three-slicer-viewer": "0.4.2"
+    "three-slicer-viewer": "0.4.3"
   }
 }