feat(storage_client): use dedicated storage host for storage lib (allows >50GB uploads) #1285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements URL transformation for the storage client to use the dedicated storage host, which disables request buffering and allows uploads up to 500GB (previously limited to ~50GB).
Context
This change matches the implementation in storage-js PR #230 and addresses Linear issue SDK-230.
The storage library was previously initialized using the same host as all other Supabase APIs (
project-ref.supabase.co/storage/v1), which has limitations for large file uploads. This change automatically transforms legacy URLs to use the dedicated storage infrastructure (project-ref.storage.supabase.co/v1).Changes
_transformStorageUrl()static method inSupabaseStorageClientto transform legacy storage URLsproject-ref.supabase.co/storage/v1→ New format:project-ref.storage.supabase.co/v1Testing
Breaking Changes
None - this is a backward-compatible change that automatically transforms legacy URLs.
Related