Early access

Pre-GA software

InertiaX is in early access. Versions are pre-stable, behavior and documentation may be incomplete or change, and breaking changes or registry/service interruptions are possible. Evaluate it before using it in production-critical work.

This page owns the temporary access and private-registry steps used before general availability. The ordinary Installation guide owns the durable Laravel and React setup.

Request access

Request early access at inertiax.dev. If admitted, you receive the current Composer and npm registry endpoints plus separate access tokens by email.

Your early-access entitlement remains active until InertiaX transitions to general availability. Registry endpoints or credentials may rotate before then; follow replacement instructions sent to your access email. General availability is expected in the coming months, but there is no fixed date or early-access SLA.

Public progress and interruption notices are posted by @yhteamdev. Credentials and account-specific instructions are sent only by email.

Connect your project

The commands below deliberately use provider-neutral placeholders. Replace the host placeholders with the endpoints in your email, and supply tokens through a secure prompt or protected environment variable. Never paste a real token into composer.json, a project .npmrc, source control, screenshots, or shared command output.

1. Configure Composer access

   Add the emailed Composer endpoint to the current project:

   composer config repositories.inertiax composer https://<composer-registry-host>

   Load YOUR_INERTIAX_COMPOSER_TOKEN into a protected environment variable named INERTIAX_COMPOSER_TOKEN, then store it in your user-level Composer authentication file. Do not commit the resulting auth file:

   composer config --global --auth bearer.<composer-registry-host> "$INERTIAX_COMPOSER_TOKEN"

   Then install the Laravel package:

   composer require inertiax/inertiax-laravel

2. Configure scoped npm access

   Log in interactively using the npm endpoint from your email:

   npm login --scope=@inertiax --registry=https://<npm-registry-host>

   Enter YOUR_INERTIAX_NPM_TOKEN only when the secure prompt requests the credential. The scoped mapping leaves ordinary public packages on your existing registry.

   Install the two frontend packages used by Laravel + React + Inertia:

   pnpm

   pnpm add @inertiax/react @inertiax/react-inertia

   npm

   npm install @inertiax/react @inertiax/react-inertia

   Yarn

   yarn add @inertiax/react @inertiax/react-inertia

   Bun

   bun add @inertiax/react @inertiax/react-inertia

Continue with the durable setup

Once both package installs succeed, continue with Installation to load the stylesheet, mount the application provider, and verify compatibility. That setup remains valid after the temporary early-access registry process is retired.

For CI, inject registry credentials from protected secrets at runtime, scope each credential to its issued host, avoid printing configuration, and remove temporary user-level auth after the job—most especially on persistent self-hosted runners.