@limrun/api 0.46.2 → 0.46.4

package/src/ios-client.ts

@@ -2385,11 +2385,13 @@ export async function createInstanceClient(options: InstanceClientOptions): Prom
     const setStoreKitConfig = async (bundleId: string, storekit: Buffer | Uint8Array): Promise<void> => {
       const body = Buffer.isBuffer(storekit) ? storekit : Buffer.from(storekit);
       const url = `${options.apiUrl}/payments/storeKitConfigs/${encodeURIComponent(bundleId)}`;
+      // No manual Content-Length: fetch computes it from the Buffer, and setting
+      // it too makes Node 22's built-in fetch send a duplicate that the npm undici
+      // proxy dispatcher rejects whenever HTTP(S)_PROXY is set.
       const response = await nodeProxyTransport.fetch(url, {
         method: 'PUT',
         headers: {
           'Content-Type': 'application/octet-stream',
-          'Content-Length': body.length.toString(),
           Authorization: `Bearer ${options.token}`,
         },
         body: body as any,

package/src/resources/assets-helpers.ts

@@ -54,9 +54,10 @@ export interface AssetGetOrUploadResponse {
 
 /**
  * Body init for the signed-URL PUT. Without a progress callback the buffer is sent
- * directly. With one, the buffer is wrapped in a ReadableStream so the callback can
- * fire as chunks are pulled onto the socket; the explicit Content-Length header set
- * by the caller keeps the request non-chunked, which signed URLs require.
+ * directly and fetch derives Content-Length from it. With one, the buffer is wrapped
+ * in a ReadableStream so the callback can fire as chunks are pulled onto the socket;
+ * the explicit Content-Length header set by the caller keeps the request non-chunked,
+ * which signed URLs require.
  */
 function uploadBodyInit(
   data: Buffer,
@@ -109,9 +110,13 @@ export class Assets extends GeneratedAssets {
         ...(creationResponse.expiresAt && { expiresAt: creationResponse.expiresAt }),
       };
     }
+    // Content-Length is set manually only for the streamed body; for the buffered
+    // body fetch computes it itself, and setting it too makes Node 22's built-in
+    // fetch send a duplicate that the npm undici proxy dispatcher rejects with
+    // "invalid content-length header" whenever HTTP(S)_PROXY is set.
     const uploadResponse = await nodeProxyTransport.fetch(creationResponse.signedUploadUrl, {
       headers: {
-        'Content-Length': data.length.toString(),
+        ...(body.onUploadProgress && { 'Content-Length': data.length.toString() }),
         'Content-Type': 'application/octet-stream',
       },
       method: 'PUT',

package/src/version.ts

@@ -1 +1 @@
-export const VERSION = '0.46.2'; // x-release-please-version
+export const VERSION = '0.46.4'; // x-release-please-version

package/version.d.mts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.46.2";
+export declare const VERSION = "0.46.4";
 //# sourceMappingURL=version.d.mts.map

package/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.46.2";
+export declare const VERSION = "0.46.4";
 //# sourceMappingURL=version.d.ts.map

package/version.js

@@ -1,5 +1,5 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
-exports.VERSION = '0.46.2'; // x-release-please-version
+exports.VERSION = '0.46.4'; // x-release-please-version
 //# sourceMappingURL=version.js.map

package/version.mjs

@@ -1,2 +1,2 @@
-export const VERSION = '0.46.2'; // x-release-please-version
+export const VERSION = '0.46.4'; // x-release-please-version
 //# sourceMappingURL=version.mjs.map