Download the PHP package manusiakemos/laravel-tanstack without Composer

Laravel DataTables for TanStack

Modern server-side datatable for Laravel, purpose-built for TanStack Table frontends (React, Vue, Svelte, Solid). Inspired by yajra/laravel-datatables but with a clean REST API instead of the legacy datatables.net protocol.

Use this when you have an Inertia (or any SPA) frontend, want server-side processing, and want to stop writing pagination + search + sort + filter boilerplate for every table.

Why this package

• Three-line endpoints. Whitelist columns, return the response. That's it.
• REST-style query string. Clean, browser-DevTools-friendly, easy to cache.
• Type-safe FE companion. Pairs with @manusiakemos/laravel-tanstack-react (separate package).
• Eloquent or Query Builder. Both supported, no extra setup.
• No jQuery, no datatables.net baggage.

Installation

Publish the config (optional):

Quick start

Register it on a web route so it has access to the session (for Inertia auth):

Done. The controller returns a JsonResponse automatically because DataTable implements Responsable.

API protocol

Request

Response

Features

Transform rows

Or use an API Resource:

Custom search

Custom sort column

For computed or relation columns:

Custom filter

Request: ?filter[created_between]=2024-01-01,2024-12-31

Authorization

Returns 403 if the closure returns false.

Default sort

Skip total count

For very large tables where count(*) over the unfiltered set is expensive:

The response will have meta.total = null; frontend should rely on filtered only.

Pagination limits

Query builder macro

For one-liner usage:

Inertia + TanStack pattern

The recommended setup: let Inertia render the page shell (layout, auth state, navigation), and let the table component fetch its own data from a separate JSON endpoint.

The table state lives in React; the page shell stays Inertia-managed. No full-page reload on pagination.

Security notes

• Never call ->searchable() or ->sortable() with untrusted column names. The package enforces whitelisting — only listed columns can be searched/sorted — but you must define the list yourself.
• Use ->authorize() for any non-public table. Or check authorization in the controller before returning the DataTable.
• The package is read-only — it does not perform writes, so SQL injection surface is limited to filter values which are bound parameters.

Configuration

The full config/laravel-tanstack.php:

Testing

Requirements

• PHP 8.2+
• Laravel 11.x or 12.x

Roadmap

• [ ] PostgreSQL-specific ILIKE search optimization
• [ ] Laravel Scout integration for full-text search
• [ ] Vue 3 and Svelte FE companions
• [ ] Excel/CSV export endpoint
• [ ] Saved view / preset support

Contributing

Contributions are welcome — bug reports, feature requests, and pull requests.

Before opening a PR:

1. Fork the repo and create a feature branch from main:

2. Install dependencies:

3. Make your change. Keep the public API stable unless the PR is explicitly a breaking change.
4. Add or update tests under tests/Feature or tests/Unit. New features without tests will not be merged.

5. Run the full quality gate locally — it must pass before you push:

6. Update CHANGELOG.md under the [Unreleased] section. Use the Keep a Changelog categories: Added, Changed, Deprecated, Removed, Fixed, Security.
7. Open the PR against main with a clear description of the change, the motivation, and any breaking-change notes.

Branch naming: feat/..., fix/..., docs/..., refactor/..., test/....

Commit style: Conventional Commits preferred (feat:, fix:, docs:, chore:, refactor:, test:).

Issues: When filing a bug, include the Laravel version, PHP version, a minimal reproduction, and the actual vs expected behavior. For feature requests, describe the use case before the proposed API.

License

MIT.