@componentor/fs 3.0.43 → 3.0.44

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@componentor/fs",
3
- "version": "3.0.43",
3
+ "version": "3.0.44",
4
4
  "description": "High-performance OPFS-based Node.js fs polyfill with true sync API, VFS binary format, and bidirectional OPFS mirroring",
5
5
  "license": "MIT",
6
6
  "author": "Componentor",
package/readme.md CHANGED
@@ -604,6 +604,21 @@ Make sure `opfsSync` is enabled (it's `true` by default). Files are mirrored to
604
604
 
605
605
  See [CHANGELOG.md](./CHANGELOG.md) for the full version history.
606
606
 
607
+ ### v3.0.44 (2026)
608
+
609
+ **Fixes:**
610
+ - Coalesce per-path OPFS sync notifications in `sync-relay.worker.ts` — a single chunked 100 MB upload now triggers one full-file read instead of ~1500, eliminating `RangeError: Array buffer allocation failed` on repeated large uploads (e.g. Strapi multipart)
611
+ - Cancel pending debounced syncs on `UNLINK`/`RMDIR`; reroute on `RENAME`
612
+ - Route `OP.SYMLINK` mirror through the same debounced flusher
613
+
614
+ **Memory:**
615
+ - Replace `scanOPFSEntries` with streaming `populateVFSFromOPFS`: chunked `SyncAccessHandle` + `engine.append`, init peak memory bounded by 2 MB instead of sum of all OPFS file sizes
616
+ - `renameInOPFS` copies via two `SyncAccessHandle`s in 2 MB chunks instead of `file.arrayBuffer()`
617
+ - Coalesce pending `write` events for the same path in the OPFS sync queue — newer payload supersedes older, frees stale `ArrayBuffer` for GC
618
+
619
+ **Tests:**
620
+ - Update `vfs-engine` test for the 100K default inode count
621
+
607
622
  ### v3.0.43 (2026)
608
623
 
609
624
  **Docs:**