supabase-js 2.0

[kiwicopple]

What?

We're using this task to plan any breaking changes that we might want to add to supabase-js as part of our 2.0 release:

(Possible) Features

• Update Type Implementation (import definitions at the constructor level): Update Type Implementation (supabase-js side) #125
• Better treeshaking: Tree shaking #151
• storage 2.0: Scratchpad for breaking changes in v2 storage-js#6
• standard error responses: Strongly Typed Errors auth-js#405
• undefined instead of null for bottom type: [Feature Request] - Option for nulls as undefined #244
• return: minimal by default
• Nested columns: Foreign Key Array supabase#535 (reply in thread)
• Default to nullsFirst: true: Supabase default of nullsLast can cause performance issues with ascending:false. postgrest-js#239

Timeline

• No fixed timeline

[inian]

supabase/storage-js#6

[soedirgo]

Re: the tree-shaking in #151, we'll be modularizing each Supabase components right? (i.e. rest, auth, etc.) Combining them into one class felt hacky to me, esp. for those with overlapping function names (e.g. from() can accept '*' in realtime-js but not postgrest-js).

This also makes it easier to implement in other languages with less flexible OO features, esp. once we tackle iOS/Android.

[soedirgo]

One more item: standardizing error response format supabase/supabase#12739 supabase/auth-js#405

[didavid61202]

must have in v2 for better TypeScript type definitions for queries, kudos to @bnjmnt4n :
supabase-client (alternative TypeScript-based)