← TanStackCONTENT HISTORY
WHAT CHANGED
Update to TanStack
Snapshot Oct 24, 2026 · 13:37 UTC · version 0.1.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save TanStack and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Introduce, add, debug, or migrate TanStack Store for a small reactive core for local application state.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 102
}
],
"name": "tanstack-store",
"skill_md_contents": "---\nname: tanstack-store\ndescription: Introduce, add, debug, or migrate TanStack Store for a small reactive core for local application state.\n---\n\n# TanStack Store\n\nA small reactive core for local application state.\n\nUse it for: Shared client state, derived values, or selected subscriptions beyond one component.\n\nUsually unnecessary for: Component-local state or cached remote data that belongs in Query.\n\n## Install and try\n\nUse the project's framework and package manager. These examples target the current official documentation checked on September 30, 2026. Match installed versions before copying them into an existing project.\n\n```sh\nnpm install @tanstack/store\n```\n\nMinimal example, run in a TypeScript module:\n\n```ts\nimport { createStore } from '@tanstack/store'\nconst count = createStore(0)\nconst double = createStore(() => count.state * 2)\ncount.setState(value => value + 1)\nconsole.log(count.state, double.state)\n```\n\nCurrent documentation uses createStore. Older installed versions expose the Store class and a different subscription cleanup contract, inspect installed guidance before migrating. Use the framework adapter for reactive rendering. Avoid putting request-specific user state in a shared server singleton.\n\n## Implement, debug, or migrate\n\nRead the project's package manifest and lockfile before changing dependencies. Load version-matched TanStack Intent guidance with `npx @tanstack/intent@latest list`, then `npx @tanstack/intent@latest load` followed by a concrete identifier returned by the list. Do not invent skill names or assume every version includes skills. If no relevant skill is packaged, use the installed version's official docs and source. Current web docs can describe a newer API than the lockfile.\n\nFor an existing project, reproduce the failure and change the smallest relevant integration. For migration, read the version-specific migration guide and preserve behavior through a small verified slice before migrating the rest. Run the project's relevant build and checks, then verify the user-visible feature. Do not add unrelated TanStack packages.\n\nIn ChatGPT without a shell or repository tools, use the connected documentation tools and provide the code and exact commands for the user to run. Never claim files were edited, packages installed, or checks passed without execution evidence.\n\n[Official docs](https://tanstack.com/store/latest/docs/overview) · [Version-matched guidance](https://tanstack.com/intent/latest/docs/overview)\n"
}SHA-256 of public snapshot: 51fb56ac4f17bfed2d0cba4285a3be479903525dd59f97e5a41ef91dadb993a9