mirror of
https://github.com/HeyPuter/puter.git
synced 2026-10-01 17:47:07 +00:00
Ayoub Ait ChikhandDaniel Salazar
790db87e13
* puter_signed_upload_error_correction * docs: update signed upload behavior * fix(puter-js): complete a bodiless response in the XHR shim A response with no body at all (`fetch` gives `null`) threw inside the shim's own `then`, the same way a missing content-type did: no 'load', no 'error', the request hangs forever. Signed storage PUTs answer in exactly that shape. Adds the regression tests the content-type fix was missing — all three hang against the shim as it was. * refactor(puter-js): drop the signed batch-write env allowlist With `nodejs`, `service-worker` and `web-worker` added, the list held every value `puter.env` can take, so the gate decided nothing — and a new env would have been silently routed to the legacy path. The backend capability check (`signedBatchWriteSupported`, set from a 404/405/501 on `startBatchWrite`) is the one that still does work. * test: run the directory-upload suite on node and workers Both were pinned to browser because the legacy `/batch` fallback cannot create a directory tree. Now that every platform takes the signed path they are the regression test for it, and the stale comment goes with them. --------- Co-authored-by: Daniel Salazar <daniel.salazar@puter.com>