@refinedev/core

@refinedev/core is the headless engine of Refine, a React meta-framework purpose-built for data-intensive enterprise applications — admin panels, dashboards, B2B tools, and internal apps. It supplies the hard parts every such app needs (authentication, access control, routing abstraction, data fetching/mutation via React Query, real-time updates, internationalization, and audit logging) as a set of hooks and providers, decoupled entirely from UI rendering and routing so it can be paired with any design system or router.

Refine ships official UI-library bindings for Ant Design, Material UI, Mantine, and Chakra UI, official data-provider connectors for 15+ backends (REST, GraphQL, Supabase, Strapi, Hasura, Airtable, NestJS CRUD, Appwrite, and more), and router bindings for Next.js, Remix, and plain React Router — making it a common choice when teams want CRUD-app scaffolding without committing to a rigid low-code platform.

What You Get

• Headless hooks for CRUD data operations (useTable, useForm, useShow, useMany, useSelect) built on React Query
• Pluggable auth and access-control providers for login, permissions, and route guarding
• Router-agnostic navigation layer with official bindings for Next.js, Remix, and React Router
• 15+ official data provider connectors (REST, GraphQL, Supabase, Strapi, Hasura, Airtable, NestJS CRUD, Appwrite, Firebase, and more)
• UI-library bindings for Ant Design, Material UI, Mantine, and Chakra UI with auto-generated CRUD components
• Built-in i18n, real-time/live updates, audit logging, and a Devtools panel for inspecting app state

Common Use Cases

• Building internal admin panels and back-office tools on top of an existing REST or GraphQL API
• Standing up B2B SaaS dashboards with authentication and role-based access control
• Rapidly scaffolding CRUD screens for a new data model without hand-rolling every table/form
• Building customer-facing storefronts or portals that need Refine’s SSR support via Next.js/Remix

Under The Hood

Architecture: @refinedev/core centers on a <Refine> context provider (src/contexts) that composes a dataProvider, routerProvider, and optional authProvider/accessControlProvider/liveProvider/notificationProvider/i18nProvider into React context, then exposes them through a large hooks surface (src/hooks, 30+ subdirectories covering auth, data, form, table, navigation, live, audit-log, i18n, and more) so any component tree can consume CRUD state without importing a specific UI or router library directly. Tech Stack: TypeScript (98% of the monorepo), built with tsup to dual ESM/CJS output, using TanStack (React) Query under the hood for caching/mutation state, and validated for package-export correctness via @arethetypeswrong/cli (attw) in CI. Code Quality: A large, mature src/ tree (300+ non-test TS/TSX files) with a parallel test/ suite, vitest as the test runner, and a monorepo-wide changesets/release process spanning 100+ tagged package releases — reflecting an actively governed, multi-package release cadence rather than a single-package project. API Design: The hook-based API (useTable, useForm, useShow) mirrors familiar React Query ergonomics, and the headless design means the same data/business-logic hooks work whether the UI is Ant Design, MUI, Mantine, Chakra, or fully custom Tailwind — a deliberate choice to keep the learning curve low for anyone who already knows React Query.