Update dependency react-table to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-table (source)	^6.11.5 → ^7.8.0

---

Release Notes

tannerlinsley/react-table (react-table)

v7.8.0

Compare Source

What's Changed

• docs: fix typo by @​FlorianCassayre in TanStack#3261
• fixed the typo in CodeSandbox link for material UI by @​chuuhtetnaing in TanStack#3555
• perf(useResizeColumns): optimize dispatch count by @​theopak in TanStack#3231
• fix: check for row existence in handleRowById by @​jschen2 in TanStack#3422
• fix(useExpanded): state of isAllRowsExpanded on React.StrictMode by @​yhor1e in TanStack#3471
• fix(useGridLayout): Support header groups by @​CollinsSpencer in TanStack#3542
• Update useSortBy docs by @​Jeffdude in TanStack#3359
• chore(deps): allow React 18 by @​chentsulin in TanStack#3873
• fix(useGroupBy): set depth on leaf rows when grouping by @​tyrdavis in TanStack#3633

New Contributors

• @​FlorianCassayre made their first contribution in TanStack#3261
• @​chuuhtetnaing made their first contribution in TanStack#3555
• @​benadam11 made their first contribution in TanStack#3769
• @​theopak made their first contribution in TanStack#3231
• @​jschen2 made their first contribution in TanStack#3422
• @​yhor1e made their first contribution in TanStack#3471
• @​CollinsSpencer made their first contribution in TanStack#3542
• @​Jeffdude made their first contribution in TanStack#3359
• @​chentsulin made their first contribution in TanStack#3873
• @​tyrdavis made their first contribution in TanStack#3633

Full Changelog: TanStack/table@v7.7.0...v7.8.0

v7.7.0

Compare Source

Features

• Add two new built in sort types (#​3235) (fa662bc)

v7.6.3

Compare Source

Bug Fixes

• provide parentRows and data to accessor (f97fb98)

v7.6.2

Compare Source

Bug Fixes

• deps: add support for React 17 (#​2852) (f1f1f78), closes #​2846

v7.6.1

Compare Source

Bug Fixes

• canNavigate check in goToPage reducer (#​2805) (a898bf0)

v7.6.0

Compare Source

Bug Fixes

• utils: Add recently removed export statement (#​2764) (a9b57eb)
• bug in sort subRows data and add test in useSortBy (#​2633) (3cba528)
• useFlexLayout: change table min width to be the sum of min width of all columns (#​2639) (d37856f)
• useRowSelect: change to toggleRowSelected reducer to use the previous state (#​2651) (1d92c6d), closes #​2171
• useRowSelect: verify row selection based on reducer state (#​2666) (0c452eb)
• useRowState: change argument for "initialRowStateAccessor" and "initialCellStateAccessor" (#​2719) (188a392), closes #​1812 #​2102 #​2701 #​2102 #​2701
• virtualized-rows: header/body column aligment (#​2711) (9f4383b)
• useExpanded - utils update (#​2738) (bd90f10)

Features

• useGridLayout: Add functionality for proposed useGridLayout (#​2525) (0c805a7)

v7.5.2

Compare Source

Bug Fixes

• do not crash when headerIdWidths is undefined (#​2754) (fc8eb99)
• useGroupBy: Improve performance (#​2757) (179f80c)

v7.5.1

Compare Source

Bug Fixes

• aggregations: min, max agg -ve num handling (#​2736) (a86e404)

v7.5.0

Compare Source

Features

• useRowSelect: Improve usePagination integration - only select rows on current page (#​2585) (205c7a9)

v7.4.2

Compare Source

Bug Fixes

• correct median aggregation calculation (6a9223b), closes #​2588

v7.4.1

Compare Source

Bug Fixes

• allow useGroupBy without useExpanded (bd6746d), closes #​2422

v7.4.0

Compare Source

Bug Fixes

• Add useExpanded in the pluginOrder because selection get broken if it's before. (#​2581) (fdb1ebe)
• initalState sortBy fix, if the last sortBy column is clicked we will replace the sort state, not toggle it (#​2508) (20ecd35)
• update tests (ec8dcb1)

Features

• useGroupBy: Set groupBy state via method (#​2570) (93e7e72)
• useSortBy: set sortBy state via method at once (#​2576) (243db86)

v7.3.5

Compare Source

Bug Fixes

• allow meta data to header via callback (#​2475) (90bf5c2)
• goToPage method (#​2502) (f3194d6)

v7.3.4

Compare Source

Bug Fixes

• useSortBy: fix the bug that causes flatRows to be incorrect when sorting and using subRows (#​2443) (b2d0aa6)

v7.3.3

Compare Source

Bug Fixes

• Use references to renderers instead of inline functions (#​2584) (aa28357)

v7.3.2

Compare Source

Bug Fixes

• Enforce useColumnOrder to be used before useGroupBy (#​2553) (7044363)

v7.3.1

Compare Source

Bug Fixes

• bug in sortData subRows (#​2541) (9676c8f)

v7.3.0

Compare Source

Features

• add reset column resizing (#​2461) (c4120e6)

v7.2.2

Compare Source

Bug Fixes

• remove scarf (d9e5593)

v7.2.1

Compare Source

Bug Fixes

• aggregations: update syntax in unique aggregation function (#​2464) (30c4be6), closes #​2173

v7.2.0

Compare Source

Bug Fixes

• layout plugins: add support for footers in layout plugins (#​2430) (afe4754)

Features

• add initialRows property on instance (#​2400) (9e59bc5)

v7.1.0

Compare Source

Bug Fixes

• typo in link to useSortBy API docs (#​2310) (7bc067c)

Features

• useFilters: add filterTypes: includesSome & includesValue (#​2329) (1d729b9)

v7.0.6

Compare Source

Bug Fixes

• detect browser support for passive events (#​2325) (fddbc19)

v7.0.5

Compare Source

v7.0.4

Compare Source

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

React Table v7 marks the culmination of over a years worth of work to refactor the entire library to a hooks-only UI/Style/Markup agnostic table building utility.

This latest version is a collection of React hooks and plugins (which are also hooks!) that help you flexibly compose logical features of the most complex data grids into a single API returned by the primary useTable hook. This API is performant, extensible, and unopinionated about markup, styles or rendering.

From the new Concepts documentation page:

React Table v7 is a headless utility, which means out of the box, it doesn't render or supply any actual UI elements. You are in charge of utilizing the state and callbacks of the hooks provided by this library to render your own table markup. Read this article to understand why React Table is built this way. If you don't want to, then here's a quick rundown anyway:

• Separation of Concerns - Not that superficial kind you read about all the time. The real kind. React Table as a library honestly has no business being in charge of your UI. The look, feel, and overall experience of your table is what makes your app or product great. The less React Table gets in the way of that, the better!
• Maintenance - By removing the massive (and seemingly endless) API surface area required to support every UI use-case, React Table can remain small, easy-to-use and simple to update/maintain.
• Extensibility - UI presents countless edge cases for a library simply because it's a creative medium, and one where every developer does things differently. By not dictating UI concerns, React Table empowers the developer to design and extend the UI based on their unique use-case.

Features from the README:

• Lightweight (5kb - 14kb+ depending on features used and tree-shaking)
• Headless (100% customizable, Bring-your-own-UI)
• Auto out of the box, fully controllable API
• Sorting (Multi and Stable)
• Filters
• Pivoting & Aggregation
• Row Selection
• Row Expansion
• Column Ordering
• Animatable
• Virtualizable
• Resizable
• Server-side/controlled data/state
• Extensible via hook-based plugin system

A special thanks!

With the help of many contributors and awesome sponsors, React Table has become a very powerful tool that will continue to support the React ecosystem for many years to come.

Well, what are you waiting for!

Go get started!

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @mui/material@5.14.0
npm ERR! Found: @emotion/styled@10.0.27
npm ERR! node_modules/@emotion/styled
npm ERR!   @emotion/styled@"^10.0.17" from @storybook/theming@5.3.21
npm ERR!   node_modules/@storybook/theming
npm ERR!     @storybook/theming@"5.3.21" from @storybook/addon-actions@5.3.21
npm ERR!     node_modules/@storybook/addon-actions
npm ERR!       @storybook/addon-actions@"^5.3.21" from the root project
npm ERR!     @storybook/theming@"5.3.21" from @storybook/addon-info@5.3.21
npm ERR!     node_modules/@storybook/addon-info
npm ERR!       dev @storybook/addon-info@"^5.3.21" from the root project
npm ERR!     2 more (@storybook/api, @storybook/components)
npm ERR!   @emotion/styled@"^10.0.4" from storybook-addon-material-ui@0.9.0-alpha.24
npm ERR!   node_modules/storybook-addon-material-ui
npm ERR!     dev storybook-addon-material-ui@"^0.9.0-alpha.24" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm ERR! node_modules/@mui/material
npm ERR!   dev @mui/material@"^5.14.0" from the root project
npm ERR!   peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm ERR!   node_modules/@mui/icons-material
npm ERR!     dev @mui/icons-material@"^5.14.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @emotion/styled@11.11.0
npm ERR! node_modules/@emotion/styled
npm ERR!   peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm ERR!   node_modules/@mui/material
npm ERR!     dev @mui/material@"^5.14.0" from the root project
npm ERR!     peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm ERR!     node_modules/@mui/icons-material
npm ERR!       dev @mui/icons-material@"^5.14.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/09c834/4741ee/cache/others/npm/_logs/2023-08-18T02_15_15_886Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/09c834/4741ee/cache/others/npm/_logs/2023-08-18T02_15_15_886Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @mui/material@5.14.0
npm error Found: @emotion/styled@10.0.27
npm error node_modules/@emotion/styled
npm error   @emotion/styled@"^10.0.17" from @storybook/theming@5.3.21
npm error   node_modules/@storybook/theming
npm error     @storybook/theming@"5.3.21" from @storybook/addon-actions@5.3.21
npm error     node_modules/@storybook/addon-actions
npm error       @storybook/addon-actions@"^5.3.21" from the root project
npm error     @storybook/theming@"5.3.21" from @storybook/addon-info@5.3.21
npm error     node_modules/@storybook/addon-info
npm error       dev @storybook/addon-info@"^5.3.21" from the root project
npm error     2 more (@storybook/api, @storybook/components)
npm error   @emotion/styled@"^10.0.4" from storybook-addon-material-ui@0.9.0-alpha.24
npm error   node_modules/storybook-addon-material-ui
npm error     dev storybook-addon-material-ui@"^0.9.0-alpha.24" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm error node_modules/@mui/material
npm error   dev @mui/material@"^5.14.0" from the root project
npm error   peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm error   node_modules/@mui/icons-material
npm error     dev @mui/icons-material@"^5.14.0" from the root project
npm error
npm error Conflicting peer dependency: @emotion/styled@11.14.1
npm error node_modules/@emotion/styled
npm error   peerOptional @emotion/styled@"^11.3.0" from @mui/material@5.14.0
npm error   node_modules/@mui/material
npm error     dev @mui/material@"^5.14.0" from the root project
npm error     peer @mui/material@"^5.0.0" from @mui/icons-material@5.14.0
npm error     node_modules/@mui/icons-material
npm error       dev @mui/icons-material@"^5.14.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-10T16_52_46_842Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-10T16_52_46_842Z-debug-0.log