- Home
- Skills
- Ponpon55837
- Mariokartworldparams
- React Table Search Pagination
react-table-search-pagination_skill
- TypeScript
0
GitHub Stars
11
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ponpon55837/mariokartworldparams --skill react-table-search-pagination- crud-sync.md15.3 KB
- infinite-scroll.md7.3 KB
- intersection-observer.md7.9 KB
- pagination-system.md9.0 KB
- race-condition.md3.7 KB
- README.md7.6 KB
- refresh-token-race-condition.md13.0 KB
- search-system.md5.7 KB
- SKILL.md10.4 KB
- state-management.md11.6 KB
- style-guide.md1.6 KB
Overview
This skill is a practical, end-to-end development guide for building tables, search, and pagination features in React and Next.js projects. It focuses on robust patterns for race condition handling, high-performance search and autocomplete, pagination and caching strategies, infinite scroll, and keeping CRUD operations consistent. The content targets TypeScript projects and recommends state management and tooling choices for different project sizes.
How this skill works
The guide inspects common async pitfalls and provides concrete implementations using AbortController, TanStack Query, and request queuing to avoid race conditions. It demonstrates search UX improvements (debounce, IME support, autocomplete), server-side and client-side pagination strategies, Intersection Observer-based infinite scroll, and CRUD synchronization patterns with optimistic updates and cache invalidation. Implementation guidance includes hooks, state choices, devtools, and performance monitoring recommendations.
When to use it
- Building list-heavy React or Next.js apps that need search, filter, and pagination
- Implementing infinite scroll or virtualized long lists for large datasets
- Preventing stale or conflicting responses in concurrent async requests
- Keeping UI and server state consistent after create, update, or delete actions
- Choosing a state-management approach based on app scale and performance needs
Best practices
- Use AbortController or request tokens to cancel outdated fetches and avoid race conditions
- Make URL the source of truth for list state (page, query, filters) to improve shareability and back/forward behavior
- Prefer TanStack Query for caching, retries, and optimistic updates; pair with lightweight state libs (Zustand/Jotai) as needed
- Debounce search input and add IME-aware logic to support multilingual typing
- Use Intersection Observer for scroll-triggered loads and preserve scroll position during navigation or data refresh
Example use cases
- A Mario Kart player directory with search, paged results, and player profile CRUD operations
- Admin dashboards that list thousands of records with filterable columns and server-side pagination
- Mobile web feeds that load more items via infinite scroll with position restore and deduplication
- Type-safe Next.js pages where query params control table state and are hydrated server-side
- Apps requiring seamless token refresh handling and queued requests without duplicate side effects
FAQ
For mid-sized apps, use TanStack Query for server data plus a lightweight client store like Zustand or Jotai for UI state; keep URL params as the canonical source for paging and filters.
How do I avoid duplicate results with infinite scroll?
Deduplicate by using stable item IDs, track loaded pages, debounce load triggers, and merge new pages into cache using query keys that include page cursors.