Use chunked transfer encoding for tar uploads

[mishushakov]

Simplify tar upload to use chunked transfer encoding instead of calculating Content-Length upfront. This eliminates the need to buffer the entire compressed tar stream in memory.

Changes:

• Remove Content-Length header from upload request
• Simplify tarFileStreamUpload to directly return the tar stream
• Let Node.js fetch handle chunked encoding automatically

---

Note

Medium Risk
Changes the upload transport semantics (no Content-Length, chunked streaming), which can affect compatibility with servers/proxies expecting a known length and could alter upload failure modes.

Overview
Switches template tarball uploads to stream directly via chunked transfer encoding instead of precomputing a Content-Length.

tarFileStreamUpload is simplified to return a single tar/gzip stream (removing the extra pass that buffered/read the stream to compute size), and uploadFile no longer sets the Content-Length header, relying on Node fetch streaming behavior. Adds a changeset to release this as an e2b patch.

^{Written by Cursor Bugbot for commit 0ff7ad3. This will update automatically on new commits. Configure here.}

[changeset-bot]

🦋 Changeset detected

Latest commit: 0ff7ad3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
e2b	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[baptistecolle]

Just tested it and it works for me.

Thanks @mishushakov!

[noamzbr]

Works for me, thanks @mishushakov!