@supabase/lite 0.2.1-next.2 → 0.3.0

package/README.md

@@ -174,7 +174,6 @@ supabase/
 ```toml
 [api]
 port = 54321
-max_rows = 1000
 
 [db]
 driver = "sqlite-postgres"    # or "sqlite" | "pglite" | "postgres"
@@ -204,7 +203,7 @@ enable_confirmations = false
 
 Write **Postgres DDL** in `supabase/schemas/*.sql`. When the DB driver is SQLite, DDL is translated on the fly (`SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`, `JSONB` → `TEXT` with a `json_valid()` check, and so on). Postgres-only features that don't translate (ranges, `LATERAL`, table inheritance) throw a descriptive error.
 
-RLS works across all backends: on SQLite, policies are extracted from DDL and enforced at the application layer by rewriting the query AST; on PGlite/Postgres, native RLS is used. `auth.uid()`, `auth.jwt()`, and roles (`anon`, `authenticated`) resolve from the JWT.
+RLS works across all backends: on SQLite, policies are extracted from DDL and enforced at the application layer by rewriting the query AST; on PGlite/Postgres, native RLS is used. `auth.uid()`, `auth.jwt()`, and roles (`anon`, `authenticated`, `service_role`) resolve from the JWT.
 
 Full translation reference: [STATUS.md#postgres-to-sqlite-translation](https://github.com/supabase-community/lite/blob/HEAD/STATUS.md#postgres-to-sqlite-translation) and [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md).
 

package/STATUS.md

@@ -34,9 +34,9 @@ Feature and API compatibility tracking for @supabase/lite. For usage docs, see [
 
 ## Postgres-to-SQLite Translation
 
-When using SQLite databases, SQL schemas written in Postgres dialect are translated on the fly. The translator extends the Postgres deparser. It passes through 1:1 compatible syntax unchanged, rewrites constructs that have SQLite equivalents (for example `SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`), silently drops Postgres-only decorators (storage parameters, locking clauses), and errors on features that have no SQLite counterpart (`LATERAL` joins, table inheritance).
+When using SQLite databases, SQL schemas written in Postgres dialect are translated on the fly. The translator extends the Postgres deparser. It passes through 1:1 compatible syntax unchanged, rewrites constructs that have SQLite equivalents (for example `SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`), silently drops Postgres-only decorators and relation/schema privilege metadata (storage parameters, locking clauses, table/schema/sequence grants), and errors on features that have no SQLite counterpart (`LATERAL` joins, table inheritance, function grants).
 
-📋 See [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md) for the full auto-generated compatibility reference (82 entries).
+📋 See [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md) for the full auto-generated compatibility reference (71 entries).
 
 Here is an example of a Postgres schema that is translated to SQLite:
 
@@ -190,7 +190,7 @@ RLS is supported on all database backends. The enforcement strategy differs by d
 
 📖 See [`internal/docs/postgres/rls.md`](https://github.com/supabase-community/lite/blob/HEAD/internal/docs/postgres/rls.md) for the full RLS reference and behavior matrix.
 
-**PGlite / PostgreSQL auto-setup:** When any table has `ENABLE ROW LEVEL SECURITY`, supalite creates `anon` and `authenticated` roles (if missing) and grants default privileges on all tables and sequences in the relevant schemas. No manual `CREATE ROLE` or `GRANT` statements needed.
+**PGlite / PostgreSQL auto-setup:** When any table has `ENABLE ROW LEVEL SECURITY`, supalite creates `anon`, `authenticated`, and `service_role` roles (if missing; `service_role` uses `BYPASSRLS`) and grants default privileges on all tables and sequences in the relevant schemas. No manual `CREATE ROLE` or `GRANT` statements needed for these built-in roles.
 
 ### PL/pgSQL Trigger Functions
 
@@ -644,7 +644,7 @@ Help groups match upstream: **Local Development** (commands you run from a proje
 
 | Command   | Status | Notes                                                              |
 |-----------|--------|--------------------------------------------------------------------|
-| `init`    | ✅      | Parity at verb level; flags differ from upstream                   |
+| `init`    | ✅      | Scaffolds API, migration/seed paths, and auth defaults; flags differ upstream |
 | `start`   | ✅      | In-process; no Docker stack flags (`-x`, `--ignore-health-check`)  |
 | `status`  | 🧪      | `[experimental]` `[lite]`: shows linked project metadata          |
 | `login`   | 🧪      | `[experimental]` Email/password against supalite cloud             |
@@ -667,11 +667,12 @@ Help groups match upstream: **Local Development** (commands you run from a proje
 
 | Command       | Status | Notes                                                                |
 |---------------|--------|----------------------------------------------------------------------|
-| `db diff`     | ✅      | Re-export of `db schema --diff` handler; `--local` semantics only    |
+| `db diff`     | ✅      | `--local` semantics; `-f` emits pg-DDL migrations from declarative schemas |
 | `db query`    | ✅      | Renamed from top-level `exec`; supports `--remote` and `--config`    |
 | `db schema`   | ✅      | `[lite]`: moved from top-level; `--diff` and `--sql` modes          |
 | `db push`     | 🔄     | Not registered; use `lite cloud deploy`                             |
-| `db pull`, `db reset`, `db dump`, `db lint`, `db advisors` | 🔄 | Not registered                       |
+| `db reset`    | ✅      | Replays migrations + seed; does not apply declarative schema_paths   |
+| `db pull`, `db dump`, `db lint`, `db advisors` | 🔄 | Not registered                       |
 | `db start`    | 🚫     | Not applicable; in-process, no separate DB start                    |
 
 ### `migration` group