mirror of
https://github.com/TanStack/db.git
synced 2026-11-16 06:56:43 +00:00
The reactive client store for your API.
https://tanstack.com/db
- TypeScript 97.7%
- JavaScript 2%
- TLA 0.2%
The mutant harness applies a mutant while Vitest transforms persisted.ts. Vitest 5 keeps transformed modules in node_modules/.vitest-cache, keyed by file and config, not by the TANSTACK_DB_MUTANT environment variable. After one run, a later run reused the cached transform, the mutant plugin never ran, and the harness reported "not applied" for a mutant that was not tested. Set test.fsModuleCache to false in vitest.mutants.config.ts. The option is documented in Vitest 5 as "Cache transformed modules on the file system and reuse them between reruns" (default true). Unmutated runs keep their cache. Evidence: - RED: after the first run, each later run reported "not applied" (P05, P06, P08, P09, P10, P18, P21, P26, P27, P28, P29, P34). The mutant plugin never wrote its mark. - GREEN: scripts/demand-coverage-mutants.mjs --only=P05 run twice in a row, with no cache cleared by hand, applied and survived both times. - The script already fails a mutant that is not applied, so a repeat of this failure is reported as BAD rather than as a survivor. Co-authored-by: Test <test@test.com> Co-authored-by: Isaac <no-reply@databricks.com> |
History
|
|
|---|---|---|
| .agents/skills | ||
| .changeset | ||
| .claude | ||
| .codex | ||
| .gemini | ||
| .github | ||
| .husky | ||
| _artifacts | ||
| docs | ||
| examples | ||
| media | ||
| notes | ||
| packages | ||
| review-evidence | ||
| scripts | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| CONTRIBUTING.md | ||
| domain_map.yaml | ||
| eslint.config.js | ||
| LICENSE | ||
| lint-staged.config.js | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| prettier.config.js | ||
| README.md | ||
| skill-tree-generator-feedback.md | ||
| skill_spec.md | ||
| todo-1785-reconciliation.md | ||
| tsconfig.json | ||
| typedoc.json | ||
TanStack DB
Tanstack DB is currently in BETA. See the release post for more details.
The reactive client store for your API.
TanStack DB solves the problems of building fast, modern apps, helping you:
- Avoid endpoint sprawl and network waterfalls by loading data into normalized collections
- Optimise client performance with sub-millisecond live queries and real-time reactivity
- Take the network off the interaction path with instant optimistic writes
Data loading is optimized. Interactions feel instantaneous. Your backend stays simple and your app stays blazing fast. No matter how much data you load.
Get Involved
- We welcome issues and pull requests!
- Participate in GitHub discussions
- Chat with the community on Discord
- See CONTRIBUTING.md for setup instructions
Partners
|
|
|
|
|
We're looking for TanStack DB Partners to join our mission! Partner with us to push the boundaries of TanStack DB and build amazing things together.
LET'S CHATExplore the TanStack Ecosystem
- TanStack Config – Tooling for JS/TS packages
- TanStack DevTools – Unified devtools panel
- TanStack Form – Type‑safe form state
- TanStack Pacer – Debouncing, throttling, batching
- TanStack Query – Async state & caching
- TanStack Ranger – Range & slider primitives
- TanStack Router – Type‑safe routing, caching & URL state
- TanStack Start – Full‑stack SSR & streaming
- TanStack Store – Reactive data store
- TanStack Table – Headless datagrids
- TanStack Virtual – Virtualized rendering
… and more at TanStack.com » v>