Skip to content
ALNEAS Ecosystem

react-tools

@alneas/react-tools

Section titled “@alneas/react-tools”

Schema forms, data tables, filters, layouts and CRUD adapters built on @alneas/react-ui. This repository owns the public implementation and uses ISC licensing. The current 0.1.0 source is a first-release candidate; registry publication is a separate step.

import { Button } from '@alneas/react-ui';
import { FormCompound, FormView } from '@alneas/react-tools/form';
import { DataTable } from '@alneas/react-tools/data-table';
import '@alneas/react-tools/styles';
// Optional application-wide reset; import before styles when needed:
// import '@alneas/react-tools/reset.css';

Basic UI and themes live in @alneas/react-ui. This package depends on its exact public version and keeps compatibility re-exports through root, /ui and /theme; there is one implementation and one theme context. The root also exports error providers, hooks and LanguageSwitcher. Composition uses render throughout. Forms and tables use their explicit subpaths. Additional entries include /core, /theme, /filter, /pane, /workflow, /sidebar, /header, /splash, /priority-queue, /editable-table, /error, /i18n, and /data-access/react. There is no root AppProvider requiring authentication or a database adapter. Generic views use /kanban, /calendar, /gantt, /file-browser and /auth. The /gantt entry also exports task-graph planning functions and types. /chart and /barcode require their optional SDK peers. SDK-specific auth adapters, PDF, Studio, visual schema tools, attendance and approval suites remain private.

Node.js 24+ and React 19 are the initial supported targets. React, React DOM, Base UI, React Hook Form and TanStack Query are shared peers. Keep one instance of their contexts in the application. The React data access bindings use @alneas/data-access; generic schema and parsing use @alneas/data-engine. Japanese holiday presets are explicit @alneas/business-jp APIs. Generic date utilities use the host locale/timezone unless supplied explicitly.

Import the prebuilt styles explicitly; no Tailwind compiler is needed by consumers. /styles provides utilities and default theme tokens without Tailwind preflight. /reset.css opts the entire application into reset rules. /theme.css exposes theme tokens separately. ThemeProvider does not import CSS as a side effect. The default font stack uses installed system fonts; this stage ships no font binary.

Translations are generated locally from messages/{en,ja,zh}.json. JSDoc defines the API. See basic usage, contributing and first-release preparation. The integrated documentation site is built by apps/docs in the public monorepo and deployed through the root Pages workflow.

See package boundaries and Storybook. Shared executable form/table examples live in examples/schema-tools.tsx and are used directly by stories.

Consumer AI setup

Section titled “Consumer AI setup”

The build generates exact exports, peer dependencies and CSS paths in dist/ai/package-context.json. Preview package-scoped project instructions with:

Terminal window
node node_modules/@alneas/react-tools/dist/ai/setup.mjs

Add --write to update bounded blocks in AGENTS.md and CLAUDE.md while preserving host instructions. Package-specific skills live in dist/ai/skills/.

React and React DOM 19 only; see peerDependencies for the minimum supported 19.x version.

Consumer AI guidance ships in dist/ai/SKILL.md and package-context.json. Preview the package-scoped additions to your project instructions with the following command. Add --write after reviewing the preview; existing instructions are preserved.

Terminal window
node node_modules/@alneas/react-tools/dist/ai/setup.mjs --project .