Upgrade to v3.1.1

Compatibility

• Use Node 24.21.0 LTS. Supported ranges are Node 22.22.2+, Node 24.15.0+, and Node 26+ as declared in each package. Node 20 is unsupported.
• Next.js 16.4.0, React 19.3.0, and the native TypeScript 7 compiler; the TypeScript 6 API alias supports framework and lint tooling.
• ESLint 10 plus Oxlint replaces the old Next ESLint preset. Vitest configuration now uses vitest.config.mts.
• Core 1.7 and TanStack Table 8 remain paired. Keep the shipped scoped dependency overrides.
• The starter now shares version 3.1.0 with the dashboard; its old 0.1.0 label was a starter identifier.

Merge and validate

Back up and commit your application first. Merge manifests and lockfiles together, then tooling, scripts, shell behavior, and styles. Preserve custom routes and data. Remove the old Vitest config; keep Framer Motion separately if your own code still uses it.

nvm use
npm ci --strict-peer-deps
npm run verify
npm run build-storybook
npx playwright install chromium firefox webkit
npx playwright test
npm run test:e2e:auth

Run these independently in the dashboard and starter. Review your own usage of upgraded third-party APIs. Full migration instructions are included as UPGRADING.md in the download.

New workflows

npm run scaffold -- page reports --dry-run
npm run scaffold -- resource support-tickets --title "Support tickets"

Try the component recipes. Demo writes reset on leaving or reloading; connect your own provider for durable records. Review intended visual changes in the pinned Linux ARM64 image described in the shipped visual-testing guide.

Authenticated backend example

The downloaded Node/SQLite server provides cookie authentication and server-side permissions. Build first, configure a private APEX_EXAMPLE_PASSWORD, then run npm run example:auth and open localhost:3740/backend-example. The static hosted preview provides an interactive workspace with disposable sample data. Local setup instructions are at /docs/backend-example.

Provisioning, recovery, multi-instance storage, and proxy-aware rate limiting remain application-specific. Existing auth screens and demo RBAC do not authorize your production API.