Restore #6284: AWS S3 rewrite by qxprakash · Pull Request #6345 · transloadit/uppy

qxprakash · 2026-06-17T08:58:20Z

restore AWS S3 rewrite #6284 to a6eddb1
sign all the commits which were authored by me and were unsigned

- base branch cleanup and ran `yarn && yarn dedupe` - client copied and tests wired up

- added `getCredentials` callback in `S3Config` - simplified signer test util ( `sigv4-signer.js` ) and moved to `src/signer.ts` - all tests run in a new non root minio user ( required for sts ) , which gets created before the tests start see `tests/s3-client/setup.js` - tests added for sts , using `@aws-sdk/client-sts` for getting creds. - credential caching inspired from the current implementation in `@aws-s3` plugin , see `#getTemporarySecurityCredentials` inside `@uppy/aws-s3/src/index.ts` --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…er.ts

#### This PR replaces signed headers with presigned urls , for signing. - I implemented this along with the uploader rewrite , but raised PR for this it separately to reduce diffs. - `signer.ts` now returns signed url , which is directly used by `_presignedRequest` method to make calls to s3 - tested it with uploader rewrite working fine. --------- Co-authored-by: Murderlon <merlijn@soverin.net>

Working : - Simple uploads (putObject) - Multipart uploads - Pause / Resume / Abort , Resume works using listParts as before - Progress tracking per chunk ( `#onProgress` ) - this is temporary , until we implement xhr based progress tracking as - before. **added new examples to examples/aws-nodejs to test the rewrite , old examples will eventually be removed** Not Yet Implemented - Rate limiting – Currently uploads are sequential - Retries - Remote file uploads – Files from Google Drive, Dropbox, etc. XHR progress - full wiring with uppy state ( I saw few state bugs while testing it manually ) --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Murderlon <merlijn@soverin.net>

Cherry-picked as the previous branch got messy ( from last PR ) - XHR-based uploads using `@uppy/utils/fetcher` - Silent offline detection (without treating it as an error) with automatic resume ( inspired from old plugin code ) - Retry with backoff using fetcher defaults: - Max retries: 3 - Delays: 300ms → 600ms → 1200ms - Retries on 5xx and 429; skips other 4xx errors - S3 Error Mappings

shouldUseMultipart: true was not working due to signature mismatch AI summary : This pull request improves support for specifying the `contentType` during S3 uploads, ensuring that the correct content type is set when generating presigned URLs for both single and multipart uploads. It also updates the client-side and server-side code to handle this new parameter. **Backend and API enhancements:** - Updated the `/s3/presign` endpoint in `index.js` to accept an optional `contentType` parameter and to include it in the S3 `PutObjectCommand` and `CreateMultipartUploadCommand` requests, defaulting to `'application/octet-stream'` if not provided. [[1]](diffhunk://#diff-0c4471088c62917198e1438777b4c7e78fd4d87d450d2a7c78b86b7c647ac97bL360-R360) [[2]](diffhunk://#diff-0c4471088c62917198e1438777b4c7e78fd4d87d450d2a7c78b86b7c647ac97bR384-R391) **Client-side and types improvements:** - Added `contentType` to the `presignableRequest` type to ensure type safety and clarity when passing this parameter. - Modified the S3 client (`S3.ts`) to include `contentType` when making presign requests. - Updated the example HTML (`rewrite-test.html`) to send `contentType` in presign requests and enabled multipart uploads for testing. [[1]](diffhunk://#diff-ca9bc28a71d2d8ac4e0aa6844698f2244594a12e695fc3e153db36674ccb2b52L103-R103) [[2]](diffhunk://#diff-ca9bc28a71d2d8ac4e0aa6844698f2244594a12e695fc3e153db36674ccb2b52R114)

- queue support added for file level concurrency.

- removed old examples , entirely remove withCustomEndpoints.html as every s3 operations are now handled by s3mini so no need of it. - add new examples and update README.md

right now whenever you upload any file through multipart upload you'll find empty body returned in `upload-success` event cause : response from completeMultipartRequest returned in CamelCase which was not parsed correctly ```xml <?xml version="1.0" encoding="UTF-8"?> <CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Location>https://testbucketnewfix.s3.eu-north-1.amazonaws.com/13febe01-8d5b-4ed3-bda1-9620fc37c694-VSCode-darwin-universal.dmg</Location><Bucket>testbucketnewfix</Bucket><Key>13febe01-8d5b-4ed3-bda1-9620fc37c694-VSCode-darwin-universal.dmg</Key><ETag>"be4129821e06a893b453f1373995202b-49"</ETag><ChecksumCRC64NVME>Wjr7mcJOfU0=</ChecksumCRC64NVME><ChecksumType>FULL_OBJECT</ChecksumType></CompleteMultipartUploadResult> ``` --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

- add support for remote uploads - add support for restore using golden-retriever - update examples - #6181 still persists --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Mikael Finstad <finstaden@gmail.com>

- update outdated examples based on latest api changes

changeset-bot · 2026-06-17T08:58:35Z

⚠️ No Changeset found

Latest commit: 1d41bcf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 49398593bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-06-17T09:11:10Z

-    this.#setResumableUploadsCapability(true)
-    return upload
+  #generateKey(file: UppyFile<M, B>): string {
+    return this.opts.generateObjectKey?.(file) ?? file.name


Generate unique S3 keys by default

With signRequest/getCredentials and no generateObjectKey, this uses the raw filename as the object key. S3 overwrites existing objects at the same key, so two uploads named image.jpg collide even though the option documentation above says the default is {randomId}-{filename}. Restore a unique default for direct S3 uploads.

Useful? React with 👍 / 👎.

it previously had the fallback to ${crypto.randomUUID()}-${file.name} we removed it in #6186 (comment) , but I think we can add the fall-back for non-companion uploads as it would help avoid collision.

upon thinking more about it , I think we shouldn't allow generateObjectKey in the common options type ( AwsS3Options ) at all. It should only live in the getCredentials and signRequest union members, since in Companion mode the object key is generated entirely on the server.

uppy/packages/@uppy/aws-s3/src/index.ts

Lines 50 to 105 in 1c0c402

export type AwsS3Options<M extends Meta, B extends Body> = PluginOpts & {

/**

* Whether to use multipart uploads.

* - `true`: Always use multipart

* - `false`: Always use simple PUT

* - `function`: Called with file, return true for multipart

* Default: Use multipart for files > 100MB

*/

shouldUseMultipart?: boolean | ((file: UppyFile<M, B>) => boolean)

getChunkSize?: (file: { size: number }) => number

allowedMetaFields?: string[] | boolean

/**

* Maximum number of files uploading concurrently.

* Each file uploads its parts sequentially.

*

* Default: 6 — chosen to match the browser's HTTP/1.1 per-origin connection

* limit. Most browsers allow 6 concurrent connections per host, so this

* prevents queueing at the browser level while maximizing throughput.

*/

limit?: number

/**

* Custom function to generate the S3 object key.

* Default: `{randomId}-{filename}`

*/

generateObjectKey?: (file: UppyFile<M, B>) => string

} & (

| {

/** S3 upload endpoint */

s3Endpoint: string

/** AWS region, required for signing */

region?: string

/**

* Function to retrieve temporary credentials for client-side signing.

* When provided, S3mini handles signing internally using SigV4.

* Alternative to signRequest or endpoint.

*/

getCredentials: IT.GetCredentialsFn

}

| {

/**

* Custom function to sign requests.

* Called with request details, should return signed headers.

* Alternative to using Companion endpoint.

*/

signRequest: IT.SignRequestFn

}

| {

/** Companion URL if you want to use Companion for signing */

companionEndpoint: string

}

)

chatgpt-codex-connector · 2026-06-17T09:11:10Z

+      request: { method: 'PUT', key },
+      data,
+      onProgress,
+      signal,
+      contentType: fileType,


Include the content type in presign requests

In signRequest mode, the signer sees only { method: 'PUT', key }, while the actual upload still sends Content-Type: fileType. If the signing backend includes ContentType in its AWS SDK command (the new Node example reads request.contentType and otherwise defaults to application/octet-stream), a non-octet file such as text/plain gets a URL signed for one content type but an XHR with another, causing S3 to reject it with a signature mismatch. Pass the content type through the presign request, and do the same for multipart creation.

Useful? React with 👍 / 👎.

I tested this manually and this is not a bug , AWS's signer simply doesn't include ContentType in the presigned url signature. ( signer used during testing was @aws-sdk/s3-request-presigner' v3. )

chatgpt-codex-connector · 2026-06-17T09:11:10Z

+      await this.#options.s3Client.createMultipartUpload(
+        this.#options.key,
+        this.#options.file.type || 'application/octet-stream',
+        this.#options.metadata,
+      )


Thread cancellation into multipart creation

When a user removes or cancels a file while createMultipartUpload() is in flight, abort() runs before #uploadId is set, so it cannot call abortMultipartUpload; because this request also does not receive the abort signal, it can still succeed afterward and leave an active multipart upload in S3 that nothing cleans up. Pass the signal into the create/list/complete client calls and clean up if it fires.

Useful? React with 👍 / 👎.

yes this is a bug I found while testing.

qxprakash · 2026-06-17T09:15:35Z

+      - name: Debug packaged uppy dependencies
+        run: |
+          rm -rf /tmp/uppy-debug
+          mkdir -p /tmp/uppy-debug
+          tar -xzf /tmp/artifacts/uppy-${{ github.sha }}.tgz --strip-components 1 -C /tmp/uppy-debug
+          node -e 'const pkg=require("/tmp/uppy-debug/package.json");const fields=["dependencies","peerDependencies","optionalDependencies","devDependencies"];let found=false;for(const f of fields){if(!pkg[f])continue;for(const [k,v] of Object.entries(pkg[f])){if(String(v).startsWith("workspace:")){console.log(`${f}: ${k}=${v}`);found=true;}}}if(!found)console.log("No workspace:* entries in packaged uppy package.json");'


I'm not sure whether this change is related to this aws-s3-rewrite PR , I'll check this

found it , Merlijn added it in PR #6151 - f80473e , it's a CI step that logs any workspace: versions leaking into the packaged tarball.

shouldn't it fail the job in case it finds one? if not, we will likely never notice

Copilot

Pull request overview

This PR restores and modernizes the @uppy/aws-s3 implementation (per the referenced AWS S3 rewrite), introducing a new browser-friendly S3 client/signing flow, Golden Retriever resume support for multipart uploads, and expanded test coverage (including MinIO-based integration tests).

Changes:

Replaces the legacy multipart implementation with a new S3Uploader + s3-client/* stack (client-side signing via STS credentials, server-side signing via signRequest, or Companion-backed signing).
Adds MinIO-backed integration tests (including Playwright browser tests) and CI wiring for VITE_MINIO_CONFIG.
Updates examples and dev dashboards to use the new option naming (companionEndpoint) and new signing flows.

Reviewed changes

Copilot reviewed 43 out of 44 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
turbo.json	Passes `VITE_MINIO_CONFIG` through Turbo test tasks to support MinIO tests.
private/dev/Dashboard.js	Updates AwsS3 dev usage to `companionEndpoint`.
packages/@uppy/utils/src/fetcher.ts	Adjusts `body` defaulting behavior in XHR fetcher.
packages/@uppy/core/src/Uppy.ts	Fixes comment typos and adds `s3Multipart` placeholder on file state.
packages/@uppy/aws-s3/vitest.config.ts	Introduces multi-project Vitest config (jsdom + Playwright browser) and global setup for MinIO.
packages/@uppy/aws-s3/tests/test-utils/browser-crypto.ts	Adds WebCrypto-based `randomBytes` helper for browser contexts.
packages/@uppy/aws-s3/tests/s3-client/setup.ts	Adds MinIO Docker compose global setup/teardown for tests.
packages/@uppy/aws-s3/tests/s3-client/minio.test.ts	Adds MinIO integration test suite for `S3mini` + STS signing.
packages/@uppy/aws-s3/tests/s3-client/docker.ts	Adds Docker helpers for starting/stopping/exec’ing in compose services.
packages/@uppy/aws-s3/tests/s3-client/config.ts	Reads `VITE_MINIO_CONFIG` and provides test credentials/config.
packages/@uppy/aws-s3/tests/s3-client/compose.minio.yaml	Adds MinIO docker-compose definition used by tests.
packages/@uppy/aws-s3/tests/index.test.ts	Adds extensive unit tests for new AwsS3 behavior and Golden Retriever resume state.
packages/@uppy/aws-s3/src/utils.ts	Removes `AwsBody` type from utils (moved to main entry).
packages/@uppy/aws-s3/src/S3Uploader.ts	New uploader handling simple + multipart uploads and resume state persistence (`s3Multipart`).
packages/@uppy/aws-s3/src/s3-client/utils.ts	Adds XML parsing, SigV4 helpers, URL sanitizers, and custom error types.
packages/@uppy/aws-s3/src/s3-client/types.ts	Adds types for presignable requests and credential/signing APIs.
packages/@uppy/aws-s3/src/s3-client/signer.ts	Adds SigV4 presigner (with backward-compatible alias).
packages/@uppy/aws-s3/src/s3-client/S3mini.ts	Adds browser-capable S3 client supporting `signRequest` or `getCredentials`.
packages/@uppy/aws-s3/src/s3-client/S3Client.ts	Adds shared XHR + retry/offline handling base class.
packages/@uppy/aws-s3/src/s3-client/index.ts	Exports `S3mini` and related types.
packages/@uppy/aws-s3/src/s3-client/consts.ts	Adds shared constants and error messages for S3 client/signing.
packages/@uppy/aws-s3/src/s3-client/CompanionS3.ts	Adds Companion-backed S3 client implementation.
packages/@uppy/aws-s3/src/MultipartUploader.ts	Deletes legacy multipart uploader implementation.
packages/@uppy/aws-s3/src/index.ts	Rewrites AwsS3 plugin API/implementation to use new uploader + signing modes.
packages/@uppy/aws-s3/src/index.test.ts	Deletes legacy AwsS3Multipart tests (replaced by `tests/index.test.ts`).
packages/@uppy/aws-s3/src/HTTPCommunicationQueue.ts	Deletes legacy HTTP communication queue.
packages/@uppy/aws-s3/src/createSignedURL.ts	Deletes legacy presigning implementation.
packages/@uppy/aws-s3/src/createSignedURL.test.ts	Deletes legacy presigning tests.
packages/@uppy/aws-s3/package.json	Adds `@aws-sdk/client-sts` dev dependency.
examples/companion-digitalocean-spaces/README.md	Updates docs links from `aws-s3-multipart` to `aws-s3`.
examples/companion-digitalocean-spaces/main.js	Updates example option to `companionEndpoint`.
examples/aws-php/s3-sign.php	Updates PHP signer example to new `signRequest` shape and improves CORS handling.
examples/aws-php/main.js	Switches example from `getUploadParameters` to `signRequest`.
examples/aws-nodejs/routes/sts.js	Adds STS credentials endpoint for client-side signing example.
examples/aws-nodejs/routes/presign.js	Adds server-side presign endpoint for `signRequest` example.
examples/aws-nodejs/README.md	Updates documentation to describe both signing modes.
examples/aws-nodejs/public/withCustomEndpoints.html	Removes the older “custom endpoints” example page.
examples/aws-nodejs/public/index.html	Updates browser example UI + wiring for both signing modes + GoldenRetriever.
examples/aws-nodejs/index.js	Refactors Node example server to use the new `routes/*` and injects bucket/region into HTML.
examples/aws-companion/main.js	Updates example option to `companionEndpoint`.
.github/workflows/ci.yml	Adds `VITE_MINIO_CONFIG` to CI env.
.github/workflows/bundlers.yml	Adds debug step to ensure packaged `uppy` doesn’t ship `workspace:*` deps.
.github/CONTRIBUTING.md	Documents how to run MinIO-backed tests locally.

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

qxprakash · 2026-06-19T18:50:23Z

+import path from 'node:path'
+import { getConfig } from './config'
+import { composeDown, composeUpWait, execDockerCommand } from './docker'
+
+const composeFile = path.join(__dirname, 'compose.minio.yaml')
+


not needed , it doesn't throw and works fine

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

…store/pr-6284

Copilot

Pull request overview

Copilot reviewed 42 out of 43 changed files in this pull request and generated 6 comments.

+// Export the S3 class as default export and named export
+export { S3mini } from './S3mini.js'


socket-security · 2026-06-19T20:09:26Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/@aws-sdk/client-sts@3.1071.0

View full report

…dback

qxprakash · 2026-06-19T20:33:42Z

@mifi most of the major comments have been addressed , for resolving merge conflicts in yarn.lock I checked out the yarn.lock of the main branch ( since it had the latest upgraded deps ) and then ran yarn install in the s3-rewrite branch to update the lockfile.

qxprakash · 2026-06-19T20:34:36Z

can you check why CI is not running ?

mifi · 2026-06-22T10:46:47Z

@copilot why is CI not running?

Copilot · 2026-06-22T10:52:32Z

@copilot why is CI not running?

Looking at the GitHub Actions history for this repo, no workflows have run at all since June 4, 2026 — this affects every branch and PR across the repository, not just this one. The CI, Bundlers, and Lockfile checks workflows all stopped triggering on that date.

This is a repository/organization-level issue, not caused by any code change in this PR. To fix it, please check:

GitHub Actions settings – Settings → Actions → General – verify "Allow all actions and reusable workflows" is selected and that Actions are not disabled.
Organization-level Actions settings – the organization may have paused/disabled Actions.
Billing / minutes quota – if the organization's paid Actions minutes were exhausted, workflows stop triggering until the quota resets or is topped up.

Once the account-level or org-level Actions issue is resolved, this PR's CI should trigger automatically on the next push/sync.

mifi · 2026-06-22T11:41:57Z

@copilot github actions was disabled repo-wise. how can i re-trigger the actions for PRs like this one now that i've enabled it?

mifi

I think I already reviewed most of this code in pretty good detail before, so I assume the code hasn't been changed after that

mifi · 2026-06-23T21:17:41Z

+      - name: Debug packaged uppy dependencies
+        run: |
+          rm -rf /tmp/uppy-debug
+          mkdir -p /tmp/uppy-debug
+          tar -xzf /tmp/artifacts/uppy-${{ github.sha }}.tgz --strip-components 1 -C /tmp/uppy-debug
+          node -e 'const pkg=require("/tmp/uppy-debug/package.json");const fields=["dependencies","peerDependencies","optionalDependencies","devDependencies"];let found=false;for(const f of fields){if(!pkg[f])continue;for(const [k,v] of Object.entries(pkg[f])){if(String(v).startsWith("workspace:")){console.log(`${f}: ${k}=${v}`);found=true;}}}if(!found)console.log("No workspace:* entries in packaged uppy package.json");'


shouldn't it fail the job in case it finds one? if not, we will likely never notice

mifi · 2026-06-23T21:21:43Z

+export const AWS_ALGORITHM = 'AWS4-HMAC-SHA256'
+export const AWS_REQUEST_TYPE = 'aws4_request'
+export const S3_SERVICE = 's3'
+export const LIST_TYPE = '2'


many of these consts are not in use anywhere. we should remove them. should also look at other code and remove that which might not be in use (maybe with the help of AI)

mifi · 2026-06-23T21:23:39Z

+
+  constructor({
+    requestAbortTimeout,
+    ...rest


Suggested change

...rest

this seems to be not in use. i wonder why biome is not complaining? maybe biome is not working properly?

mifi · 2026-06-23T21:25:54Z

+        console.warn(
+          `[S3mini] Upload stalled - no progress for ${Math.ceil(timeout / 1000)}s`,
+        )


I think we should remove all console logging from Uppy. If we need logging we could pass a logger into the client. If it's only this line, maybe just remove it (or allow the user to provide an onTimeout option and pass it to that)

mifi · 2026-06-23T21:32:59Z

-  location: string
-  key: string
-  bucket: string
-}


throwIfAborted and most of the types in this file (below), like UploadResultWithSignal are unused, and should be removed

qxprakash and others added 14 commits June 17, 2026 13:54

add s3mini client to @uppy/aws-s3 plugin (#6103)

6b9521f

- base branch cleanup and ran `yarn && yarn dedupe` - client copied and tests wired up

give credit

db9506a

remove HTTPCommunication queue and clean index.ts and MultipartUplaod…

e7f62dd

…er.ts

remove tests

a3ca750

@uppy/aws-s3 add queue (#6171)

779c19c

- queue support added for file level concurrency.

update aws-nodejs examples (#6187)

50de6d1

- removed old examples , entirely remove withCustomEndpoints.html as every s3 operations are now handled by s3mini so no need of it. - add new examples and update README.md

@uppy/aws-s3: update examples (#6311)

4939859

- update outdated examples based on latest api changes

remove .claude/worktrees gitlink

1c0c402

chatgpt-codex-connector Bot reviewed Jun 17, 2026

View reviewed changes

qxprakash requested a review from Copilot June 17, 2026 09:12

Copilot started reviewing on behalf of qxprakash June 17, 2026 09:12 View session

qxprakash commented Jun 17, 2026

View reviewed changes

Copilot AI reviewed Jun 17, 2026

View reviewed changes

qxprakash and others added 3 commits June 20, 2026 00:49

exclude minio.test.ts from jsdom test

113a5c5

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

revert body = null in fetcher

f88e037

Merge branch 'restore/pr-6284' of github.com:transloadit/uppy into re…

1b36024

…store/pr-6284

qxprakash requested a review from Copilot June 19, 2026 19:56

Copilot started reviewing on behalf of qxprakash June 19, 2026 19:56 View session

Copilot AI reviewed Jun 19, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into restore/pr-6284

5585a79

update comments , update type casing and update examples based on fee…

9f88450

…dback

fix lint based on new biome rules after merge

1d41bcf

qxprakash requested a review from mifi June 19, 2026 20:35

Copilot started work on behalf of mifi June 22, 2026 10:47 View session

Copilot finished work on behalf of mifi June 22, 2026 10:52

mifi reviewed Jun 23, 2026

View reviewed changes

	export type AwsS3Options<M extends Meta, B extends Body> = PluginOpts & {
	/**
	* Whether to use multipart uploads.
	* - `true`: Always use multipart
	* - `false`: Always use simple PUT
	* - `function`: Called with file, return true for multipart
	* Default: Use multipart for files > 100MB
	*/
	shouldUseMultipart?: boolean \| ((file: UppyFile<M, B>) => boolean)
	getChunkSize?: (file: { size: number }) => number
	allowedMetaFields?: string[] \| boolean

	/**
	* Maximum number of files uploading concurrently.
	* Each file uploads its parts sequentially.
	*
	* Default: 6 — chosen to match the browser's HTTP/1.1 per-origin connection
	* limit. Most browsers allow 6 concurrent connections per host, so this
	* prevents queueing at the browser level while maximizing throughput.
	*/
	limit?: number

	/**
	* Custom function to generate the S3 object key.
	* Default: `{randomId}-{filename}`
	*/
	generateObjectKey?: (file: UppyFile<M, B>) => string
	} & (
	\| {
	/** S3 upload endpoint */
	s3Endpoint: string

	/** AWS region, required for signing */
	region?: string

	/**
	* Function to retrieve temporary credentials for client-side signing.
	* When provided, S3mini handles signing internally using SigV4.
	* Alternative to signRequest or endpoint.
	*/
	getCredentials: IT.GetCredentialsFn
	}
	\| {
	/**
	* Custom function to sign requests.
	* Called with request details, should return signed headers.
	* Alternative to using Companion endpoint.
	*/
	signRequest: IT.SignRequestFn
	}
	\| {
	/** Companion URL if you want to use Companion for signing */
	companionEndpoint: string
	}
	)

		// Export the S3 class as default export and named export
		export { S3mini } from './S3mini.js'

Uh oh!

Conversation

qxprakash commented Jun 17, 2026

Uh oh!

changeset-bot Bot commented Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jun 17, 2026

Choose a reason for hiding this comment

Uh oh!

qxprakash Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jun 17, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jun 17, 2026

Choose a reason for hiding this comment

Uh oh!

qxprakash Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

qxprakash Jun 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

qxprakash Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

socket-security Bot commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qxprakash commented Jun 19, 2026

Uh oh!

qxprakash commented Jun 19, 2026

Uh oh!

mifi commented Jun 22, 2026

Uh oh!

Copilot AI commented Jun 22, 2026

Uh oh!

mifi commented Jun 22, 2026

Uh oh!

mifi left a comment

Choose a reason for hiding this comment

Uh oh!

changeset-bot Bot commented Jun 17, 2026 •

edited

Loading

qxprakash Jun 19, 2026 •

edited

Loading

qxprakash Jun 19, 2026 •

edited

Loading

qxprakash Jun 17, 2026 •

edited

Loading

qxprakash Jun 19, 2026 •

edited

Loading

socket-security Bot commented Jun 19, 2026 •

edited

Loading