Bobbie Soedirgo
Bobbie Soedirgo
There are more pressing issues right now, esp. wrt functionality - once the client libs are stable enough we'll look into how to refactor them to support tree-shaking.
Hmm, the websocket package isn't that big actually ([1.1KB](https://bundlephobia.com/package/websocket)), but yeah that'd help trim it down. Though a bigger win would be from omitting `cross-fetch` ([2.8KB](https://bundlephobia.com/package/[email protected])) on environments that don't...
Thanks all! Some updates on reducing the bundle size: - we're in the process of replacing `cross-fetch` with [just `node-fetch`](https://github.com/supabase/postgrest-js/pull/462), which should shave around 3kB - we're planning to remove...
I suppose this falls under https://github.com/supabase/supabase/discussions/357 - the client lib is the right place for it.
I can't reproduce this on the sample project with `npm run dev`. > and deployment target should've set up; I used CloudFlare Can you clarify what this means? Are you...
+1, I realized after the fact that e.g. the [TypeScript coding guidelines](https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines#null-and-undefined) (caveat: read the title) uses only `undefined` as the bottom type and forbids `null`. There isn't much point...
@danielpox thanks for the input! Yes, in https://github.com/supabase/postgrest-js/pull/278 we decided to adopt the Prisma team's stance on this. We do use `undefined` instead of `null` for function args etc., but...
Not sure about Auth and Realtime, but for REST this should be fine. Alternatively (and this is a bit hacky): ```js // initSupabase.js let currentFetch; export function setFetch(fetch) { //...
There shouldn't be an issue with using multiple clients, so closing this.
Seems like an issue on cross-fetch: https://github.com/lquixada/cross-fetch/issues/120#issuecomment-1617172860 Can you run `npm up @supabase/postgrest-js` and see if the error changes? We're about to replace cross-fetch with using node-fetch directly which can...