Investigate removing the dependency on Query DB Collection
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- supabase, typescript
- Domain
- backend-api-design, databases
Research direction
No file, test, or entry point is named. Start by tracing the Supabase collection adapter and its use of @tanstack/query-db-collection, then compare keeping, wrapping, and replacing that dependency. Done means documenting its current role, Supabase-specific tradeoffs, a recommendation, and a safe follow-up plan if removal is advised.
Written by the indexing model from the issue text.
Description
What to build
Investigate whether the Supabase collection adapter should continue depending on @tanstack/query-db-collection, wrap it more narrowly, or replace it with a direct TanStack DB collection implementation.
The current dependency provides a useful bridge between TanStack Query and TanStack DB, but it may also constrain Supabase-specific behavior such as Realtime subscription lifecycle, PostgREST pagination, optimistic writes, rollback, and future offline support. This issue should evaluate whether the dependency is still the right foundation as the adapter matures.
The outcome should be a design recommendation, not a large refactor by default. If removal is recommended, document the smallest safe migration path, expected public API changes, test coverage needed, and whether users should observe any behavior changes.
Acceptance criteria
- Explain what
@tanstack/query-db-collectionprovides to this adapter today. - Identify the Supabase-specific behaviors it helps or constrains.
- Compare keeping it, wrapping it, and replacing it with a direct adapter.
- Recommend a path forward with tradeoffs.
- If removal is recommended, outline a safe follow-up implementation plan.
Blocked by
None - can start immediately.
- Dominant language
- TypeScript
- Stars
- 57
- Forks
- 5
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/tanstack-db
-
enhancement ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 35/100
supabase/tanstack-db#12 ·
-
enhancement ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 35/100
supabase/tanstack-db#10 · 2 comments ·
-
enhancement ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 56/100
supabase/tanstack-db#9 · 1 comment ·
-
enhancement ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 64/100
supabase/tanstack-db#8 ·
All issues in supabase/tanstack-db
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·