@drawbridge/drawbridge-utils 0.0.99 → 0.0.101

package/dist/ai.cjs

@@ -168,6 +168,16 @@ var cost = {
     input: 150,
     output: 900
   },
+  // gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+  // $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+  // output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+  // ranks the feed on this tier — one call per page — so its rows were the
+  // unpriced ones until now.
+  "gemini-3.5-flash-lite": {
+    cached: 3,
+    input: 30,
+    output: 250
+  },
   "gemini-2.5-flash": {
     cached: 3,
     input: 30,

package/dist/ai.js

@@ -134,6 +134,16 @@ var cost = {
     input: 150,
     output: 900
   },
+  // gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+  // $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+  // output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+  // ranks the feed on this tier — one call per page — so its rows were the
+  // unpriced ones until now.
+  "gemini-3.5-flash-lite": {
+    cached: 3,
+    input: 30,
+    output: 250
+  },
   "gemini-2.5-flash": {
     cached: 3,
     input: 30,

package/dist/billing.cjs

@@ -168,6 +168,16 @@ var cost = {
     input: 150,
     output: 900
   },
+  // gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+  // $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+  // output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+  // ranks the feed on this tier — one call per page — so its rows were the
+  // unpriced ones until now.
+  "gemini-3.5-flash-lite": {
+    cached: 3,
+    input: 30,
+    output: 250
+  },
   "gemini-2.5-flash": {
     cached: 3,
     input: 30,

package/dist/billing.d.cts

@@ -39,6 +39,16 @@ const cost = {
 		input : 150,
 		output : 900
 	},
+	// gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+	// $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+	// output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+	// ranks the feed on this tier — one call per page — so its rows were the
+	// unpriced ones until now.
+	'gemini-3.5-flash-lite' : {
+		cached : 3,
+		input : 30,
+		output : 250
+	},
 	'gemini-2.5-flash' : {
 		cached : 3,
 		input : 30,

package/dist/billing.d.ts

@@ -39,6 +39,16 @@ const cost = {
 		input : 150,
 		output : 900
 	},
+	// gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+	// $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+	// output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+	// ranks the feed on this tier — one call per page — so its rows were the
+	// unpriced ones until now.
+	'gemini-3.5-flash-lite' : {
+		cached : 3,
+		input : 30,
+		output : 250
+	},
 	'gemini-2.5-flash' : {
 		cached : 3,
 		input : 30,

package/dist/billing.js

@@ -138,6 +138,16 @@ var cost = {
     input: 150,
     output: 900
   },
+  // gemini-3.5-flash-lite — verified against Google's pricing page 2026-08-20:
+  // $0.03 cached / $0.30 input / $2.50 output per 1M tokens (thinking billed at
+  // output). A fifth of flash on input, ~a quarter on output. Growth's assistant
+  // ranks the feed on this tier — one call per page — so its rows were the
+  // unpriced ones until now.
+  "gemini-3.5-flash-lite": {
+    cached: 3,
+    input: 30,
+    output: 250
+  },
   "gemini-2.5-flash": {
     cached: 3,
     input: 30,

package/dist/features.cjs

@@ -68,7 +68,7 @@ var field = {
     feature: "Campaign name field"
   },
   number: {
-    key: "campaign:field:name",
+    key: "campaign:field:number",
     error: "Plan does not include number field",
     feature: "Campaign number field"
   },

package/dist/features.d.cts

@@ -41,7 +41,7 @@ const field = {
 		feature : 'Campaign name field',
 	},
 	number : {
-		key : 'campaign:field:name',
+		key : 'campaign:field:number',
 		error : 'Plan does not include number field',
 		feature : 'Campaign number field',
 	},

package/dist/features.d.ts

@@ -41,7 +41,7 @@ const field = {
 		feature : 'Campaign name field',
 	},
 	number : {
-		key : 'campaign:field:name',
+		key : 'campaign:field:number',
 		error : 'Plan does not include number field',
 		feature : 'Campaign number field',
 	},

package/dist/features.js

@@ -40,7 +40,7 @@ var field = {
     feature: "Campaign name field"
   },
   number: {
-    key: "campaign:field:name",
+    key: "campaign:field:number",
     error: "Plan does not include number field",
     feature: "Campaign number field"
   },

package/dist/fetch.cjs

@@ -32,8 +32,7 @@ __export(fetch_exports, {
   isTransientError: () => isTransientError,
   queryString: () => queryString,
   request: () => request,
-  setMemoryToken: () => setMemoryToken,
-  upload: () => upload
+  setMemoryToken: () => setMemoryToken
 });
 module.exports = __toCommonJS(fetch_exports);
 var import_qs = __toESM(require("qs"), 1);
@@ -123,59 +122,6 @@ var request = async ({
   }
   return res;
 };
-var upload = ({
-  body,
-  endpoint,
-  method = "POST",
-  onProgress,
-  signal,
-  token,
-  url = process.env.NEXT_PUBLIC_API_URI
-}) => {
-  const authToken = token || (typeof window !== "undefined" ? memoryToken : null);
-  const csrf = readCsrf();
-  return new Promise((resolve, reject) => {
-    const xhr = new XMLHttpRequest();
-    xhr.open(method, url + endpoint, true);
-    xhr.setRequestHeader("accept", "application/json");
-    if (authToken) {
-      xhr.setRequestHeader("authorization", "Bearer " + authToken);
-    }
-    if (csrf) {
-      xhr.setRequestHeader("x-drawbridge-csrf", csrf);
-    }
-    xhr.upload.addEventListener("progress", (event) => {
-      if (!event.lengthComputable || !onProgress) return;
-      onProgress({
-        bytesTotal: event.total,
-        bytesUploaded: event.loaded
-      });
-    });
-    xhr.addEventListener("load", () => {
-      let data = null;
-      try {
-        data = JSON.parse(xhr.responseText);
-      } catch {
-        data = null;
-      }
-      if (xhr.status >= 200 && xhr.status < 300) return resolve(data);
-      const error = new Error((data == null ? void 0 : data.message) || xhr.statusText);
-      error.status = xhr.status;
-      error.data = data;
-      reject(error);
-    });
-    xhr.addEventListener("abort", () => {
-      const error = new Error("Upload cancelled");
-      error.name = "AbortError";
-      reject(error);
-    });
-    xhr.addEventListener("error", () => reject(new Error("Network error")));
-    if (signal) {
-      signal.addEventListener("abort", () => xhr.abort(), { once: true });
-    }
-    xhr.send(body);
-  });
-};
 var isTransientError = (error) => {
   const status = error == null ? void 0 : error.status;
   return !status || status === 429 || status >= 500;
@@ -185,6 +131,5 @@ var isTransientError = (error) => {
   isTransientError,
   queryString,
   request,
-  setMemoryToken,
-  upload
+  setMemoryToken
 });

package/dist/fetch.d.cts

@@ -124,118 +124,6 @@ const request = async ({
 
 };
 
-// fetch() has no upload-progress event and never will, which is the reason every
-// upload in the dashboard could only ever show a spinner. XHR does, so anything
-// that wants a real progress bar posts through here instead.
-//
-// It lives beside request() rather than in the dashboard because `memoryToken`
-// above is module-private on purpose — a copy in app-web could only read it if
-// the token were exported, which is the one thing setMemoryToken exists to
-// prevent. The csrf cookie read is here too.
-//
-// The error shape is deliberately identical to request()'s — an Error carrying
-// .status and .data — so isTransientError() and every existing catch block work
-// against either transport without knowing which ran.
-const upload = ({
-	body,
-	endpoint,
-	method = 'POST',
-	onProgress,
-	signal,
-	token,
-	url = process.env.NEXT_PUBLIC_API_URI
-}) => {
-
-	const authToken = token || ( typeof window !== 'undefined' ? memoryToken : null );
-	const csrf = readCsrf();
-
-	return new Promise( ( resolve, reject ) => {
-
-		const xhr = new XMLHttpRequest();
-
-		xhr.open( method, url + endpoint, true );
-
-		// No content-type, ever. The browser has to write the multipart boundary
-		// itself and setting the header by hand drops it, which busboy then
-		// rejects. Nor origin: it is a forbidden header name, so the browser
-		// ignores setRequestHeader for it ( request() only sets it because its
-		// server-side callers run where fetch allows it ).
-		xhr.setRequestHeader( 'accept', 'application/json' );
-
-		if( authToken ){
-
-			xhr.setRequestHeader( 'authorization', 'Bearer ' + authToken );
-
-		}
-
-		if( csrf ){
-
-			xhr.setRequestHeader( 'x-drawbridge-csrf', csrf );
-
-		}
-
-		xhr.upload.addEventListener( 'progress', ( event ) => {
-
-			if( ! event.lengthComputable || ! onProgress ) return;
-
-			onProgress({
-				bytesTotal : event.total,
-				bytesUploaded : event.loaded
-			});
-
-		});
-
-		xhr.addEventListener( 'load', () => {
-
-			let data = null;
-
-			try {
-
-				data = JSON.parse( xhr.responseText );
-
-			} catch {
-
-				data = null;
-
-			}
-
-			if( xhr.status >= 200 && xhr.status < 300 ) return resolve( data );
-
-			const error = new Error( data?.message || xhr.statusText );
-
-			error.status = xhr.status;
-			error.data = data;
-
-			reject( error );
-
-		});
-
-		xhr.addEventListener( 'abort', () => {
-
-			const error = new Error( 'Upload cancelled' );
-
-			error.name = 'AbortError';
-
-			reject( error );
-
-		});
-
-		// No status on a network failure, which is exactly how isTransientError
-		// classifies it — worth a retry rather than a sign-in bounce.
-		xhr.addEventListener( 'error', () => reject( new Error( 'Network error' ) ) );
-
-		if( signal ){
-
-			signal.addEventListener( 'abort', () => xhr.abort(), { once : true } );
-
-		}
-
-		xhr.send( body );
-
-	});
-
-};
-
 // Classifies an error thrown by request() — which carries `.status` from the
 // HTTP response, or no status for a network / parse failure. Transient errors
 // ( rate limits, server errors, connection blips ) may succeed on retry, so
@@ -251,4 +139,4 @@ const isTransientError = ( error ) => {
 
 };
 
-export { isTransientError, queryString, request, setMemoryToken, upload };
+export { isTransientError, queryString, request, setMemoryToken };

package/dist/fetch.d.ts

@@ -124,118 +124,6 @@ const request = async ({
 
 };
 
-// fetch() has no upload-progress event and never will, which is the reason every
-// upload in the dashboard could only ever show a spinner. XHR does, so anything
-// that wants a real progress bar posts through here instead.
-//
-// It lives beside request() rather than in the dashboard because `memoryToken`
-// above is module-private on purpose — a copy in app-web could only read it if
-// the token were exported, which is the one thing setMemoryToken exists to
-// prevent. The csrf cookie read is here too.
-//
-// The error shape is deliberately identical to request()'s — an Error carrying
-// .status and .data — so isTransientError() and every existing catch block work
-// against either transport without knowing which ran.
-const upload = ({
-	body,
-	endpoint,
-	method = 'POST',
-	onProgress,
-	signal,
-	token,
-	url = process.env.NEXT_PUBLIC_API_URI
-}) => {
-
-	const authToken = token || ( typeof window !== 'undefined' ? memoryToken : null );
-	const csrf = readCsrf();
-
-	return new Promise( ( resolve, reject ) => {
-
-		const xhr = new XMLHttpRequest();
-
-		xhr.open( method, url + endpoint, true );
-
-		// No content-type, ever. The browser has to write the multipart boundary
-		// itself and setting the header by hand drops it, which busboy then
-		// rejects. Nor origin: it is a forbidden header name, so the browser
-		// ignores setRequestHeader for it ( request() only sets it because its
-		// server-side callers run where fetch allows it ).
-		xhr.setRequestHeader( 'accept', 'application/json' );
-
-		if( authToken ){
-
-			xhr.setRequestHeader( 'authorization', 'Bearer ' + authToken );
-
-		}
-
-		if( csrf ){
-
-			xhr.setRequestHeader( 'x-drawbridge-csrf', csrf );
-
-		}
-
-		xhr.upload.addEventListener( 'progress', ( event ) => {
-
-			if( ! event.lengthComputable || ! onProgress ) return;
-
-			onProgress({
-				bytesTotal : event.total,
-				bytesUploaded : event.loaded
-			});
-
-		});
-
-		xhr.addEventListener( 'load', () => {
-
-			let data = null;
-
-			try {
-
-				data = JSON.parse( xhr.responseText );
-
-			} catch {
-
-				data = null;
-
-			}
-
-			if( xhr.status >= 200 && xhr.status < 300 ) return resolve( data );
-
-			const error = new Error( data?.message || xhr.statusText );
-
-			error.status = xhr.status;
-			error.data = data;
-
-			reject( error );
-
-		});
-
-		xhr.addEventListener( 'abort', () => {
-
-			const error = new Error( 'Upload cancelled' );
-
-			error.name = 'AbortError';
-
-			reject( error );
-
-		});
-
-		// No status on a network failure, which is exactly how isTransientError
-		// classifies it — worth a retry rather than a sign-in bounce.
-		xhr.addEventListener( 'error', () => reject( new Error( 'Network error' ) ) );
-
-		if( signal ){
-
-			signal.addEventListener( 'abort', () => xhr.abort(), { once : true } );
-
-		}
-
-		xhr.send( body );
-
-	});
-
-};
-
 // Classifies an error thrown by request() — which carries `.status` from the
 // HTTP response, or no status for a network / parse failure. Transient errors
 // ( rate limits, server errors, connection blips ) may succeed on retry, so
@@ -251,4 +139,4 @@ const isTransientError = ( error ) => {
 
 };
 
-export { isTransientError, queryString, request, setMemoryToken, upload };
+export { isTransientError, queryString, request, setMemoryToken };

package/dist/fetch.js

@@ -86,59 +86,6 @@ var request = async ({
   }
   return res;
 };
-var upload = ({
-  body,
-  endpoint,
-  method = "POST",
-  onProgress,
-  signal,
-  token,
-  url = process.env.NEXT_PUBLIC_API_URI
-}) => {
-  const authToken = token || (typeof window !== "undefined" ? memoryToken : null);
-  const csrf = readCsrf();
-  return new Promise((resolve, reject) => {
-    const xhr = new XMLHttpRequest();
-    xhr.open(method, url + endpoint, true);
-    xhr.setRequestHeader("accept", "application/json");
-    if (authToken) {
-      xhr.setRequestHeader("authorization", "Bearer " + authToken);
-    }
-    if (csrf) {
-      xhr.setRequestHeader("x-drawbridge-csrf", csrf);
-    }
-    xhr.upload.addEventListener("progress", (event) => {
-      if (!event.lengthComputable || !onProgress) return;
-      onProgress({
-        bytesTotal: event.total,
-        bytesUploaded: event.loaded
-      });
-    });
-    xhr.addEventListener("load", () => {
-      let data = null;
-      try {
-        data = JSON.parse(xhr.responseText);
-      } catch {
-        data = null;
-      }
-      if (xhr.status >= 200 && xhr.status < 300) return resolve(data);
-      const error = new Error((data == null ? void 0 : data.message) || xhr.statusText);
-      error.status = xhr.status;
-      error.data = data;
-      reject(error);
-    });
-    xhr.addEventListener("abort", () => {
-      const error = new Error("Upload cancelled");
-      error.name = "AbortError";
-      reject(error);
-    });
-    xhr.addEventListener("error", () => reject(new Error("Network error")));
-    if (signal) {
-      signal.addEventListener("abort", () => xhr.abort(), { once: true });
-    }
-    xhr.send(body);
-  });
-};
 var isTransientError = (error) => {
   const status = error == null ? void 0 : error.status;
   return !status || status === 429 || status >= 500;
@@ -147,6 +94,5 @@ export {
   isTransientError,
   queryString,
   request,
-  setMemoryToken,
-  upload
+  setMemoryToken
 };

package/dist/plans.cjs

@@ -78,7 +78,7 @@ var field = {
     feature: "Campaign name field"
   },
   number: {
-    key: "campaign:field:name",
+    key: "campaign:field:number",
     error: "Plan does not include number field",
     feature: "Campaign number field"
   },

package/dist/plans.js

@@ -40,7 +40,7 @@ var field = {
     feature: "Campaign name field"
   },
   number: {
-    key: "campaign:field:name",
+    key: "campaign:field:number",
     error: "Plan does not include number field",
     feature: "Campaign number field"
   },

package/dist/upload.cjs

@@ -22,10 +22,7 @@ __export(upload_exports, {
   allowedMimes: () => allowedMimes,
   allowedUploadTypes: () => allowedUploadTypes,
   isAllowedMime: () => isAllowedMime,
-  maximumUploadBytes: () => maximumUploadBytes,
-  resolveUploadType: () => resolveUploadType,
-  uploadPartCount: () => uploadPartCount,
-  uploadPartSize: () => uploadPartSize
+  resolveUploadType: () => resolveUploadType
 });
 module.exports = __toCommonJS(upload_exports);
 var allowedUploadTypes = {
@@ -39,11 +36,6 @@ var allowedUploadTypes = {
     webp: "image/webp"
   },
   video: {
-    // iPhones record .mov (HEVC) by default, so this is the single most
-    // likely video a merchant uploads. sync's storage.js already computes
-    // needsReencode for hevc/h265 and re-encodes to h264, so allowing it
-    // here is the only thing the pipeline was waiting on.
-    mov: "video/quicktime",
     mp4: "video/mp4"
   }
 };
@@ -64,27 +56,10 @@ var resolveUploadType = (type, extension) => {
   return mime;
 };
 var isAllowedMime = (mime) => allowedMimes.has(mime);
-var megabyte = 1024 * 1024;
-var maximumUploadBytes = 2048 * megabyte;
-var maximumParts = 9e3;
-var minimumPartSize = 10 * megabyte;
-var uploadPartSize = (bytes) => {
-  const size = Number(bytes) || 0;
-  const required = Math.ceil(size / maximumParts);
-  const rounded = Math.ceil(required / megabyte) * megabyte;
-  return Math.max(minimumPartSize, rounded);
-};
-var uploadPartCount = (bytes) => {
-  const size = Number(bytes) || 0;
-  return Math.max(1, Math.ceil(size / uploadPartSize(size)));
-};
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
   allowedMimes,
   allowedUploadTypes,
   isAllowedMime,
-  maximumUploadBytes,
-  resolveUploadType,
-  uploadPartCount,
-  uploadPartSize
+  resolveUploadType
 });

package/dist/upload.d.cts

@@ -15,12 +15,6 @@
 //
 // Why both helpers and not just one: api routes know (type, extension) but not
 // the canonical mime; sync workers have the mime but not the original type tuple.
-//
-// A third consumer joined with presigned multipart uploads: the dashboard reads
-// this same object to build its file picker's accept attribute and the uploader's
-// client-side restrictions, so a wrong type is refused before two gigabytes move
-// rather than after. That is the whole reason the list is not copied into
-// app-web — four views of one list can't drift.
 
 const allowedUploadTypes = {
 	application : {
@@ -33,11 +27,6 @@ const allowedUploadTypes = {
 		webp : 'image/webp'
 	},
 	video : {
-		// iPhones record .mov (HEVC) by default, so this is the single most
-		// likely video a merchant uploads. sync's storage.js already computes
-		// needsReencode for hevc/h265 and re-encodes to h264, so allowing it
-		// here is the only thing the pipeline was waiting on.
-		mov : 'video/quicktime',
 		mp4 : 'video/mp4'
 	}
 };
@@ -66,51 +55,4 @@ const resolveUploadType = ( type, extension ) => {
 
 const isAllowedMime = ( mime ) => allowedMimes.has( mime );
 
-const megabyte = ( 1024 * 1024 );
-
-// The ceiling for a presigned multipart upload. Video streams browser-to-bucket
-// on that path rather than through the api, so this is a product decision
-// rather than the fleet-protection one that keeps the single-request busboy
-// route at 50MB.
-//
-// It lives here because both sides have to agree on it exactly: the dashboard
-// rejects before transferring and the api rejects authoritatively, and if the
-// two numbers drift the client blocks files the api would happily accept.
-const maximumUploadBytes = ( 2048 * megabyte );
-
-// S3 caps a multipart upload at 10,000 parts and requires every part except the
-// last to be at least 5MB. A fixed part size therefore puts a silent ceiling on
-// the maximum file, so the size is derived from the declared length with
-// headroom against the hard limit.
-//
-// The 10MB floor is a request-volume decision, not an S3 one: a 2GB upload at
-// 5MB parts is 410 signing calls, at 10MB it is 205.
-//
-// Both the api and the dashboard call this, and the dashboard *must* — Uppy
-// builds its chunk list in the MultipartUploader constructor, which runs before
-// createMultipartUpload is ever called, so a part size returned from the create
-// endpoint arrives too late to chunk with. One function, two callers, no
-// possibility of disagreeing about where the part boundaries fall.
-const maximumParts = 9000;
-const minimumPartSize = ( 10 * megabyte );
-
-const uploadPartSize = ( bytes ) => {
-
-	const size = Number( bytes ) || 0;
-	const required = Math.ceil( size / maximumParts );
-	const rounded = Math.ceil( required / megabyte ) * megabyte;
-
-	return Math.max( minimumPartSize, rounded );
-
-};
-
-// An empty upload is still one part — S3 has no zero-part upload.
-const uploadPartCount = ( bytes ) => {
-
-	const size = Number( bytes ) || 0;
-
-	return Math.max( 1, Math.ceil( size / uploadPartSize( size ) ) );
-
-};
-
-export { allowedMimes, allowedUploadTypes, isAllowedMime, maximumUploadBytes, resolveUploadType, uploadPartCount, uploadPartSize };
+export { allowedMimes, allowedUploadTypes, isAllowedMime, resolveUploadType };

package/dist/upload.d.ts

@@ -15,12 +15,6 @@
 //
 // Why both helpers and not just one: api routes know (type, extension) but not
 // the canonical mime; sync workers have the mime but not the original type tuple.
-//
-// A third consumer joined with presigned multipart uploads: the dashboard reads
-// this same object to build its file picker's accept attribute and the uploader's
-// client-side restrictions, so a wrong type is refused before two gigabytes move
-// rather than after. That is the whole reason the list is not copied into
-// app-web — four views of one list can't drift.
 
 const allowedUploadTypes = {
 	application : {
@@ -33,11 +27,6 @@ const allowedUploadTypes = {
 		webp : 'image/webp'
 	},
 	video : {
-		// iPhones record .mov (HEVC) by default, so this is the single most
-		// likely video a merchant uploads. sync's storage.js already computes
-		// needsReencode for hevc/h265 and re-encodes to h264, so allowing it
-		// here is the only thing the pipeline was waiting on.
-		mov : 'video/quicktime',
 		mp4 : 'video/mp4'
 	}
 };
@@ -66,51 +55,4 @@ const resolveUploadType = ( type, extension ) => {
 
 const isAllowedMime = ( mime ) => allowedMimes.has( mime );
 
-const megabyte = ( 1024 * 1024 );
-
-// The ceiling for a presigned multipart upload. Video streams browser-to-bucket
-// on that path rather than through the api, so this is a product decision
-// rather than the fleet-protection one that keeps the single-request busboy
-// route at 50MB.
-//
-// It lives here because both sides have to agree on it exactly: the dashboard
-// rejects before transferring and the api rejects authoritatively, and if the
-// two numbers drift the client blocks files the api would happily accept.
-const maximumUploadBytes = ( 2048 * megabyte );
-
-// S3 caps a multipart upload at 10,000 parts and requires every part except the
-// last to be at least 5MB. A fixed part size therefore puts a silent ceiling on
-// the maximum file, so the size is derived from the declared length with
-// headroom against the hard limit.
-//
-// The 10MB floor is a request-volume decision, not an S3 one: a 2GB upload at
-// 5MB parts is 410 signing calls, at 10MB it is 205.
-//
-// Both the api and the dashboard call this, and the dashboard *must* — Uppy
-// builds its chunk list in the MultipartUploader constructor, which runs before
-// createMultipartUpload is ever called, so a part size returned from the create
-// endpoint arrives too late to chunk with. One function, two callers, no
-// possibility of disagreeing about where the part boundaries fall.
-const maximumParts = 9000;
-const minimumPartSize = ( 10 * megabyte );
-
-const uploadPartSize = ( bytes ) => {
-
-	const size = Number( bytes ) || 0;
-	const required = Math.ceil( size / maximumParts );
-	const rounded = Math.ceil( required / megabyte ) * megabyte;
-
-	return Math.max( minimumPartSize, rounded );
-
-};
-
-// An empty upload is still one part — S3 has no zero-part upload.
-const uploadPartCount = ( bytes ) => {
-
-	const size = Number( bytes ) || 0;
-
-	return Math.max( 1, Math.ceil( size / uploadPartSize( size ) ) );
-
-};
-
-export { allowedMimes, allowedUploadTypes, isAllowedMime, maximumUploadBytes, resolveUploadType, uploadPartCount, uploadPartSize };
+export { allowedMimes, allowedUploadTypes, isAllowedMime, resolveUploadType };

package/dist/upload.js

@@ -10,11 +10,6 @@ var allowedUploadTypes = {
     webp: "image/webp"
   },
   video: {
-    // iPhones record .mov (HEVC) by default, so this is the single most
-    // likely video a merchant uploads. sync's storage.js already computes
-    // needsReencode for hevc/h265 and re-encodes to h264, so allowing it
-    // here is the only thing the pipeline was waiting on.
-    mov: "video/quicktime",
     mp4: "video/mp4"
   }
 };
@@ -35,26 +30,9 @@ var resolveUploadType = (type, extension) => {
   return mime;
 };
 var isAllowedMime = (mime) => allowedMimes.has(mime);
-var megabyte = 1024 * 1024;
-var maximumUploadBytes = 2048 * megabyte;
-var maximumParts = 9e3;
-var minimumPartSize = 10 * megabyte;
-var uploadPartSize = (bytes) => {
-  const size = Number(bytes) || 0;
-  const required = Math.ceil(size / maximumParts);
-  const rounded = Math.ceil(required / megabyte) * megabyte;
-  return Math.max(minimumPartSize, rounded);
-};
-var uploadPartCount = (bytes) => {
-  const size = Number(bytes) || 0;
-  return Math.max(1, Math.ceil(size / uploadPartSize(size)));
-};
 export {
   allowedMimes,
   allowedUploadTypes,
   isAllowedMime,
-  maximumUploadBytes,
-  resolveUploadType,
-  uploadPartCount,
-  uploadPartSize
+  resolveUploadType
 };

package/package.json

@@ -179,5 +179,5 @@
     "test": ". \"$HOME/.nvm/nvm.sh\" && nvm use && node --test"
   },
   "types": "dist/index.d.ts",
-  "version": "0.0.99"
+  "version": "0.0.101"
 }