better-supabase 0.7.0 → 0.8.0

package/skills/better-supabase/references/troubleshooting.md

@@ -7,24 +7,24 @@ Start with `pnpm better-supabase doctor`. It checks the database, RLS,
 
 Branch on `result.error.kind`, not on the message.
 
-| Kind                                                  | Usual cause                                                                    | Fix                                                                           |
-| ----------------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
-| `not_found`                                           | The row doesn't exist, or RLS hides it from this user                          | Check the policy with an `asUser` test before assuming the row is gone        |
-| `unauthorized`                                        | No valid session or token                                                      | Get `db` from the adapter for this request                                    |
-| `forbidden`                                           | RLS or a grant rejected the write                                              | Fix the policy or the grant; don't switch to `bs.admin()`                     |
-| `conflict`                                            | Unique violation                                                               | Use `upsert`, or return the error to the caller                               |
-| `foreign_key`                                         | Referenced row missing, or still referenced on delete                          | Create the parent first, or delete children                                   |
-| `not_null`, `check`, `exclusion`                      | A constraint rejected the row                                                  | Validate input earlier with the `validation()` plugin                         |
-| `invalid_input`                                       | Postgres couldn't parse a value (bad uuid, enum)                               | Validate before the call                                                      |
-| `invalid_value`                                       | A stored value the app type can't hold (`infinity` in a Temporal timestamp)    | Store a real timestamp or `null`, or read the column without the codec        |
-| `validation`                                          | A Standard Schema rejected the input; see `issues`                             | Show the issues to the user                                                   |
-| `invalid_request`                                     | The query can't run over PostgREST (for example a relation filter on `update`) | Read the keys first, or use a database function or `better-supabase/postgres` |
-| `multiple_rows`                                       | `findUnique` or a single-row write matched more than one row                   | Filter by a unique key                                                        |
-| `stale`                                               | `update(..., { expect })` found a newer row                                    | Reload the row and retry                                                      |
-| `serialization`, `timeout`, `network`, `rate_limited` | Transient                                                                      | Retry with backoff, or surface the error                                      |
-| `unsupported`                                         | The executor can't run the query, such as an include on SQLite (PowerSync)     | Read it on the server, or check list definitions with `checkSqlite` in a test |
-| `raised`                                              | A database function raised an exception                                        | Read `message` and `code` from the function                                   |
-| `unexpected` naming `temporal-polyfill/global`        | The runtime has no `Temporal` (Node 24, Safari)                                | Pass `temporal: Temporal` from `temporal-polyfill` to `defineSupabase`        |
+| Kind                                                  | Usual cause                                                                    | Fix                                                                                                         |
+| ----------------------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
+| `not_found`                                           | The row doesn't exist, or RLS hides it from this user                          | Check the policy with an `asUser` test before assuming the row is gone                                      |
+| `unauthorized`                                        | No valid session or token                                                      | Get `db` from the adapter for this request                                                                  |
+| `forbidden`                                           | RLS or a grant rejected the write                                              | Fix the policy or the grant; don't switch to `bs.admin()`                                                   |
+| `conflict`                                            | Unique violation                                                               | Use `upsert`, or return the error to the caller                                                             |
+| `foreign_key`                                         | Referenced row missing, or still referenced on delete                          | Create the parent first, or delete children                                                                 |
+| `not_null`, `check`, `exclusion`                      | A constraint rejected the row                                                  | Validate input earlier with the `validation()` plugin                                                       |
+| `invalid_input`                                       | Postgres couldn't parse a value (bad uuid, enum)                               | Validate before the call                                                                                    |
+| `invalid_value`                                       | A stored value the app type can't hold (`infinity` in a Temporal timestamp)    | Store a real timestamp or `null`, or read the column without the codec                                      |
+| `validation`                                          | A Standard Schema rejected the input; see `issues`                             | Show the issues to the user                                                                                 |
+| `invalid_request`                                     | The query can't run over PostgREST (for example a relation filter on `update`) | Read the keys first, or use a database function or `better-supabase/postgres`                               |
+| `multiple_rows`                                       | `findUnique` or a single-row write matched more than one row                   | Filter by a unique key                                                                                      |
+| `stale`                                               | `update(..., { expect })` found a newer row                                    | Reload the row and retry                                                                                    |
+| `serialization`, `timeout`, `network`, `rate_limited` | Transient                                                                      | Retry with backoff, or surface the error                                                                    |
+| `unsupported`                                         | The executor can't run the query, such as an include on SQLite (PowerSync)     | Read it on the server, set the PowerSync `fallback`, or check list definitions with `checkSqlite` in a test |
+| `raised`                                              | A database function raised an exception                                        | Read `message` and `code` from the function                                                                 |
+| `unexpected` naming `temporal-polyfill/global`        | The runtime has no `Temporal` (Node 24, Safari)                                | Pass `temporal: Temporal` from `temporal-polyfill` to `defineSupabase`                                      |
 
 ## By error `code`
 
@@ -51,8 +51,8 @@ Branch on `result.error.kind`, not on the message.
 - The CLI exits with 2: the command line, the config or an environment
   variable needs a change. Rerun with `--json` to get the error `code`, and
   look it up at https://bettersupabase.com/docs/cli/errors.
-- `--db-url` is rejected: set `$DATABASE_URL` or pipe the URL in with
-  `--db-url-stdin`.
+- `--db-url` is rejected: set `$DATABASE_URL` or `$SUPABASE_DB_URL`, or pipe
+  the URL in with `--db-url-stdin`.
 - Two different `Temporal.Instant` values compare equal in `toEqual`: compare
   with `.equals()` or register an equality tester (the
   `better-supabase-testing` skill).

package/skills/better-supabase-api/references/expo.md

@@ -2,9 +2,11 @@
 
 ## Server (web): `better-supabase/expo`
 
-Needs `expo-server` 55 or later and, in `app.json`, `web.output: "server"`
-plus the `expo-router` plugin options `unstable_useServerDataLoaders` and
-`unstable_useServerMiddleware`.
+Needs `expo-server` 55 or later and, in `app.json`, `web.output: "server"`.
+On Expo SDK 57 and earlier, also set the `expo-router` plugin options
+`unstable_useServerDataLoaders`, `unstable_useServerMiddleware` and
+`unstable_useServerRendering`. SDK 58 needs no opt-in; the three options are
+deprecated there and have no effect.
 
 ```ts title="src/lib/supabase/server.ts"
 import { createExpo } from "better-supabase/expo";
@@ -27,6 +29,7 @@ export default bs.middleware();
 - Loaders run as the caller (bearer token first, then the cookie), so RLS applies.
 - A refused caller and a `DbException` from `.orThrow()` become a `StatusError` with the right status.
 - Only `+middleware.ts` refreshes the session; loaders never do.
+- `bs.loader` returns an `expo-server` `LoaderFunction`. Inside an existing `createServerLoader(async (request, params) => ...)`, call `const { db } = await bs.request(request, { allow })`. Static rendering has no request: use `createStaticLoader` from `expo-server` for public data there.
 - Loader data is JSON: select the columns the screen needs and turn Temporal values into strings.
 - API routes: `export const GET = bs.handler((request, { db }) => db.customers.findMany())` in `+api.ts`.
 

package/skills/better-supabase-api/references/powersync.md

@@ -8,7 +8,8 @@ export const local = betterSupabase.connect(powersyncExecutor(powersync));
 
 - `local.customers.findMany(...)` and `list.run(local, query)` run on the device's SQLite database and return the same rows (casing, Temporal values) as PostgREST.
 - Live results: `watch(powersync, () => list.run(local, query), { tables: sqliteTables(betterSupabase, ["customers"]), onResult })`.
-- Includes, related counts, full-text search, `db.rpc` and writes to tables without a primary key return a `DbError` of kind `unsupported`. Assert `checkSqlite(betterSupabase, list)` in a test for every list a native screen runs.
+- Includes, related counts, full-text search, `db.$rpc` and writes to tables without a primary key return a `DbError` of kind `unsupported`. Assert `checkSqlite(betterSupabase, list, { all: true })` is `[]` in a test for every list a native screen runs.
+- `powersyncExecutor(powersync, { fallback: postgrestExecutor(supabase, betterSupabase.executorOptions()) })` sends unsupported reads and `$rpc` to PostgREST (online only); writes never fall back. In `watch`, a fallback read reruns only on local changes to `tables`. Prefer syncing a summary table through sync rules when the screen must work offline.
 - `ilike` is SQLite `like` (case-insensitive for ASCII only).
 
 ## Uploading local writes

package/skills/better-supabase-auth/SKILL.md

@@ -115,10 +115,14 @@ A proxy or middleware with its own Supabase client calls
 Done when the irreversible action returns `SESSION_REVOKED` for a signed-out
 session in a test.
 
-To lock a user out, call `bs.suspendAccount(userId, { suspended: true })`
-(it bans the user in Auth and ends every session and refresh token), or
-`bs.endSessions(userId)` to sign them out everywhere without a ban. A ban
-alone leaves the refresh tokens, which work again once the ban is lifted. To
+To lock a user out, call `bs.suspendAccount(userId, { suspended: true })`.
+It bans the user in Auth and keeps the sessions, so Auth answers with
+`user_banned`, `sessionStatus` returns `"banned"` and the `session_active()`
+policy refuses the user's tokens. `{ suspended: false }` ends every session
+and refresh token, then lifts the ban. Without the `sessions` SQL module, pass
+`endSessions: true` to delete the sessions on suspension too (the app then
+sees `"ended"`). `bs.endSessions(userId)` signs a user out everywhere without
+a ban. To
 switch a member off in one organization only, use the organizations block's
 `suspendMember`.
 

package/dist/cli/config-B9HkL8nF.js

@@ -1,2 +0,0 @@
-import { a as loadConfig, i as importExport, n as discoverConfig, o as readSupabasePort, r as findConfig, s as stdinDatabaseUrl, t as databaseUrl } from "./config-NiPxAmUF.js";
-export { databaseUrl, discoverConfig, findConfig, importExport, loadConfig, readSupabasePort, stdinDatabaseUrl };