\n}\n```\n\n## Entry points\n\n| import | what you get |\n| --- | --- |\n| `@octanejs/tanstack-table` | everything `@tanstack/table-core` exports + `useTable`, `Subscribe`, `flexRender`, `FlexRender`, `createTableHook`, `createTableHookContexts` |\n| `@octanejs/tanstack-table/flex-render` | `flexRender` / `FlexRender` alone |\n| `@octanejs/tanstack-table/static-functions` | table-core's static function surface |\n| `@octanejs/tanstack-table/experimental-worker-plugin` | table-core's experimental worker plugin |\n\n## State and re-renders\n\nv9 keeps every state slice in a TanStack Store atom. `useTable` supplies octane's\nreactivity bindings to table-core, then subscribes with `useSelector`:\n\n```tsx\n// Subscribe to everything (default).\nconst table = useTable({ features, data, columns });\ntable.state.sorting;\n\n// Or project, and only re-render when the projection changes (shallow compare).\nconst table = useTable({ features, data, columns }, (state) => ({\n pagination: state.pagination,\n}));\ntable.state.pagination;\n```\n\nFor finer-grained updates, keep the component subscribed to little or nothing and\nopt in lower down with `table.Subscribe`:\n\n```tsx\n state.rowSelection}>\n {(rowSelection) => {Object.keys(rowSelection).length as unknown as string}}\n\n\n// Or subscribe to a single atom directly.\n\n {(rowSelection) => …}\n\n```\n\n## Strong-mode snapshot boundaries\n\nThis binding is pinned to `@tanstack/react-table@9.2.4`. In that v9\nadapter, `useTable` returns a reactive wrapper whose `state` and `options` are\nfresh for the current render, while table-core row, header, and column objects\nremain stable live objects. A compatibility component may read their methods\nwhen its subscription rerenders it. Do not pass one of those objects into a\nStrong component and call `row.getIsSelected()` or\n`header.column.getIsSorted()` there: unchanged object identity is not an\nimmutable snapshot.\n\nSubscribe and select on the compatibility side, then pass the selected value\nthrough the Strong boundary:\n\n```tsx\n// Compatibility module\nfunction SelectionBridge({ table, row }) @{\n !!selection[row.id]}\n >\n {(selected) => }\n \n}\n```\n\n```tsx\n// StrongRow.tsrx\n\"use strong\";\n\nfunction StrongRow({ label, selected }) @{\n
{label}
\n}\n```\n\nThe conformance suite exercises this handoff with inline `.map`, keyed `@for`,\nand an extracted compatibility subscriber. It asserts selected and sorted\noutput plus keyed DOM identity in development and production compilation.\nShallow-copying a row or forcing a render without selecting the changing value\ndoes not create a snapshot and is intentionally unsupported in Strong mode.\n\n## Composition with `createTableHook`\n\n`createTableHook` is the table equivalent of TanStack Form's `createFormHook`:\ndeclare features and reusable components once, then read the instance from\ncontext inside them.\n\n```tsx\nexport const { useAppTable, createAppColumnHelper, useCellContext } = createTableHook({\n features,\n cellComponents: { TextCell },\n tableComponents: { RowCount },\n});\n\nfunction TextCell() @{\n const cell = useCellContext();\n {cell.getValue() as string}\n}\n\nfunction UsersTable() @{\n const table = useAppTable({ data, columns });\n \n \n
\n \n @for (const row of table.getRowModel().rows; key row.id) {\n
\n @for (const c of row.getAllCells(); key c.id) {\n \n {(cell) =>
}\n \n }\n
\n }\n \n
\n \n}\n```\n\n## How it works\n\n`useTable` creates the table instance once and hands table-core a\n`coreReactivityFeature` binding built on TanStack Store atoms (imported through\n`@octanejs/tanstack-store`, which re-exports all of `@tanstack/store`), then\nsynchronizes options during every render so props (`data`, `columns`, controlled\nstate, feature handlers) land before any read. The returned object is\nre-created each render so `table.state` and `table.options` are the values read\nduring *that* render; the underlying instance, its store, and its atoms are\nstable for the component's lifetime.\n\n`flexRender` triages a columnDef renderer: components render through octane's\n`createElement` descriptor; strings, numbers, and pre-created elements pass\nthrough as-is. Upstream's class-component and `react.memo`/`forwardRef`\nexotic-object branches are dropped — octane has no class components or\n`forwardRef`, and octane's `memo()` returns a plain function.\n\noctane keys hooks by a compiler-injected per-call-site `Symbol`, appended as the\nlast argument of every `use*` call. Because `useTable` and `useAppTable` end in\nan *optional* `selector` parameter, both split that trailing slot off their rest\nargs (see `src/internal.ts`) — otherwise `useTable(options)` would read the slot\nsymbol as the selector.\n\n## Not ported\n\nUpstream's `useLegacyTable` entry — the v8-compatibility shim with `get*RowModel`\nmarker factories and `Legacy*` type aliases — is deliberately absent. It exists to\nmigrate existing React v8 codebases; octane has none, so octane code targets the\nv9 `useTable` API directly.\n\n## Status\n\nCurrent scope, known divergences, and verification status are tracked in the\ngenerated [bindings status table](../../docs/bindings-status.md), sourced from\nthis package's [`status.json`](./status.json).\n\n## Legacy migration\n\nImport `useLegacyTable`, row-model marker factories and the `Legacy*` types from\n`@octanejs/tanstack-table/legacy` when migrating v8 options. New tables use the\nv9 `useTable` feature API. The native instance type is `LegacyOctaneTable`.\n\nControlled options are staged during render and published after commit. During a\nheld transition, raw store observers can receive the unchanged committed snapshot\nfrom Octane's pending-cue render; suspended state is never published.\n","readmeFilename":""}