You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a built-in PocketBase add-on for React (--add-ons pocketbase).
PocketBase is an open source backend in a single binary: embedded SQLite, auth, realtime subscriptions, file storage and an admin UI. It's a popular choice for side projects and self-hosted apps, and right now the CLI has no self-hosted backend option in the database category (Neon, Convex and PowerSync are all hosted services).
Scope
It follows the same shape as the existing Convex / PowerSync add-ons:
Thanks for putting this together! Could you link the implementation or open a draft PR so we can review what you already have?
AI review notes:
Please include the SDK and PocketBase server versions used, the generated migration, and how collection permissions keep one user from reading or changing another user’s todos. Local setup and test commands would help us verify the integration without contacting a hosted backend. We can preserve your implementation and credit rather than build a competing add-on.
Permissions: my first version had public rules, so I changed it after your question. Todos now have a required owner relation, and the collection's API rules restrict list, view, update, delete and realtime events to the owner. The create and update rules also stop a user from creating a todo for someone else or handing one over.
Local setup and tests: the commands are in the PR, along with a script that checks these permissions against a local PocketBase server.
The PR lists what I ran. I don't have branded Chrome, so I ran the E2E suite on headless Chromium with a local config.
Activity
tannerlinsley commentedon Nov 6, 2026
Thanks for putting this together! Could you link the implementation or open a draft PR so we can review what you already have?
akanyane commentedon Nov 6, 2026
Thanks! Draft PR is up: #572
It has what you asked for:
^0.28.2.pb_migrations/1761955200_created_todos.js.ownerrelation, and the collection's API rules restrict list, view, update, delete and realtime events to the owner. The create and update rules also stop a user from creating a todo for someone else or handing one over.The PR lists what I ran. I don't have branded Chrome, so I ran the E2E suite on headless Chromium with a local config.