Integration: Data Tables

[endigo9740]

This will act as a hub to centralize this information.

Maintainer Requests

The following requests are coming straight from the Skeleton team. These are highly likely be implemented:

Note

We're aiming to retire the dedicated Table component in Skeleton v3 in favor of styled native HTML tables via the Tailwind Components (aka "Element"). This will help reduce common issues as listed below. As well as provide better integration of third party data table solutions:

• React: https://tanstack.com/table/latest
• Svelte: https://github.com/vincjo/datatables

Reference:

• https://jamesoclaire.com/2025/04/09/easiest-way-to-get-tanstack-table-v8-working-with-svelte-5/

Bugs and Known Issues

• Does not integrate with third party data table libraries
• Does not allow for components to be inserted into table cells
• Is difficult to style due to the structure
• The table data utilities are more confusing than helpful

Feedback

If you have additional updates or requests for this feature, please do so in the comments section below.

[kmalloy24]

TanStack's Svelte Adapter for runes looks ready to go TanStack/table#5403

[endigo9740]

@kmalloy24 I actually did review the Tanstack Tables for Svelte at least a year or so ago. The docs were in a really rough shape at the time. Links that went to empty pages, etc. As long as that's improved I'd be open to exploring this. Looks like they provide support for all major frameworks though, so I'm down. I'd say maybe start with an audit before committing to the guide though.

Also note I have no solid plans for the Paginator component yet. It's hard to avoid building these in an opinionated manner. Which can be troublesome when there's no single standard for pagination structure and functionality. Plus you need to support both local client-side and remote server-side pagination options. We might lean into the options provided by the library we opt for. So maybe keep that in mind as you explore.

[kmalloy24]

I only looked briefly, but they seem fairly fleshed out now. It's mostly the same as the core docs, but with some Svelte specific stuff for handling state. Once they push the runes update I'll see if I can get an example working.

Pagination is tricky...good point. I ran into an issue when trying to use the old guide to paginate data from Supabase and ended up just using range from postgres through their API and linking it up to some buttons.

[endigo9740]

Awesome, and yeah we'll definitely need Svelte 5 support. v3 is going all in on that.

As for pagination, just let us know if you think it makes sense to add a component or not. We've been moving v2 features to proposed Cookbook recipes. Basically teach folks how to build it rather than building it for them. That gives them to flexibility to adjust per their use cases. So we have options.

[kmalloy24]

I like that, especially since a framework agnostic solution wouldn't be that useful to most folks wanting to take advantage of ways to work with framework specific features like the page store in sveltekit or something. Will keep you posted 👍