Fix: Update file buffer handling to use BinaryLike for improved data integrity

[Aryan0699]

Description

When computing the SHA256 hash of uploaded files, we were using a Node.js Buffer directly. However, the Node.js crypto API requires a stricter type called BinaryLike, which doesn't fully accept Buffer in newer TypeScript versions

Solution :

Converted the Buffer to Uint8Array (a standard binary type) using Uint8Array.from(fileBuffer).

The fix is minimal (one line change) and has zero impact on actual functionality—it's purely a type compatibility improvement.

Resolved or fixed issue

none

Affirmation

• My code follows the CONTRIBUTING.md guidelines

[vercel]

@Aryan0699 is attempting to deploy a commit to the shopstr-eng Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR adjusts SHA256 hashing input types for uploaded files to satisfy newer TypeScript expectations around Node.js crypto’s BinaryLike input.

Changes:

• Adds a BinaryLike type import and converts the upload buffer to Uint8Array before hashing
• Updates size reporting to use the new binary data length

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[GautamBytes]

Nit pick:

Consider reusing binaryData in the upload body instead of creating another Uint8Array:
body: new Blob([binaryData], { type: params.mimeType }),

This keeps the binary handling consistent throughout the function.

[Aryan0699]

Actually it was giving a type error when i tried to do that saying that expected was ArrayBuffer but got ArrayBufferLike .
Should i update it still or will this work ?

[GautamBytes]

Actually it was giving a type error when i tried to do that saying that expected was ArrayBuffer but got ArrayBufferLike . Should i update it still or will this work ?

no issues, good as it is.
LGTM