Merge branch 'main' into add-autofocus-support and resolve conflicts

Author: rorychatt

.github/docker/Dockerfile.docs

@@ -6,17 +6,26 @@ WORKDIR /app
 EXPOSE 5010
 
 # Build frontend (Ivy embeds frontend/dist)
-FROM node:20-alpine AS frontend
+FROM node:24-bookworm-slim AS frontend
 WORKDIR /src
-COPY ["src/frontend/package.json", "src/frontend/package-lock.json", "src/frontend/"]
-RUN cd src/frontend && npm ci
+COPY ["src/frontend/package.json", "src/frontend/pnpm-lock.yaml", "src/frontend/"]
+RUN apt-get update && apt-get install -y curl bash && rm -rf /var/lib/apt/lists/*
+RUN curl -fsSL https://vite.plus | bash
+ENV PATH="/root/.vite-plus/bin:${PATH}"
+RUN cd src/frontend && vp install
 COPY ["src/frontend/", "src/frontend/"]
-RUN cd src/frontend && npm run build
+RUN cd src/frontend && vp build
 
 # Build .NET from source (no IVY_PACKAGE_VERSION = use ProjectReference, your changes apply)
 FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
 ARG BUILD_CONFIGURATION=Release
 WORKDIR /src
+RUN apt-get update && apt-get install -y curl bash build-essential && rm -rf /var/lib/apt/lists/*
+RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash -s -- -y
+ENV PATH="/root/.cargo/bin:${PATH}"
+RUN curl -fsSL https://deb.nodesource.com/setup_22.x | bash - && apt-get install -y nodejs
+RUN curl -fsSL https://vite.plus | bash
+ENV PATH="/root/.vite-plus/bin:${PATH}"
 COPY . .
 COPY --from=frontend /src/src/frontend/dist /src/src/frontend/dist
 RUN dotnet restore "src/Ivy.Docs/Ivy.Docs.csproj"

.github/docker/Dockerfile.samples

@@ -6,17 +6,26 @@ WORKDIR /app
 EXPOSE 5010
 
 # Build frontend (Ivy embeds frontend/dist)
-FROM node:20-alpine AS frontend
+FROM node:24-bookworm-slim AS frontend
 WORKDIR /src
-COPY ["src/frontend/package.json", "src/frontend/package-lock.json", "src/frontend/"]
-RUN cd src/frontend && npm ci
+COPY ["src/frontend/package.json", "src/frontend/pnpm-lock.yaml", "src/frontend/"]
+RUN apt-get update && apt-get install -y curl bash && rm -rf /var/lib/apt/lists/*
+RUN curl -fsSL https://vite.plus | bash
+ENV PATH="/root/.vite-plus/bin:${PATH}"
+RUN cd src/frontend && vp install
 COPY ["src/frontend/", "src/frontend/"]
-RUN cd src/frontend && npm run build
+RUN cd src/frontend && vp build
 
 # Build .NET from source (no IVY_PACKAGE_VERSION = use ProjectReference, your changes apply)
 FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
 ARG BUILD_CONFIGURATION=Release
 WORKDIR /src
+RUN apt-get update && apt-get install -y curl bash build-essential && rm -rf /var/lib/apt/lists/*
+RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash -s -- -y
+ENV PATH="/root/.cargo/bin:${PATH}"
+RUN curl -fsSL https://deb.nodesource.com/setup_22.x | bash - && apt-get install -y nodejs
+RUN curl -fsSL https://vite.plus | bash
+ENV PATH="/root/.vite-plus/bin:${PATH}"
 COPY . .
 COPY --from=frontend /src/src/frontend/dist /src/src/frontend/dist
 RUN dotnet restore "src/Ivy.Samples/Ivy.Samples.csproj"

.github/workflows/backend-checks-linux.yml

@@ -8,7 +8,10 @@ on:
     branches: [main, master]
 jobs:
   backend-checks:
-    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        os: [ubuntu-latest, ubuntu-24.04-arm64]
+    runs-on: ${{ matrix.os }}
     defaults:
       run:
         working-directory: src
@@ -19,6 +22,9 @@ jobs:
       - name: Install required packages
         run: sudo apt-get update && sudo apt-get install -y attr
 
+      # Setup Node.js (needed for integrated frontend build in dotnet build)
+      - uses: voidzero-dev/setup-vp@v1
+
       # Setup .NET
       - name: Setup .NET
         uses: actions/setup-dotnet@v4

.github/workflows/backend-checks-windows.yml

@@ -15,6 +15,9 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
+      # Setup Node.js (needed for integrated frontend build in dotnet build)
+      - uses: voidzero-dev/setup-vp@v1
+
       # Setup .NET
       - name: Setup .NET
         uses: actions/setup-dotnet@v4

.github/workflows/e2e-docs-tests.yml

@@ -13,20 +13,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      # Setup Node.js and frontend first
-      - uses: actions/setup-node@v4
-        with:
-          node-version: lts/*
-
-      - name: Install frontend dependencies
-        working-directory: ./src/frontend
-        run: npm ci
-
-      - name: Build frontend
-        working-directory: ./src/frontend
-        run: npm run build
+      # Setup Node.js (needed for integrated frontend build in dotnet build)
+      - uses: voidzero-dev/setup-vp@v1
 
-      # Setup .NET and build backend (now with frontend assets available)
+      # Setup .NET and build backend (triggers frontend build automatically)
       - name: Setup .NET
         uses: actions/setup-dotnet@v4
         with:

.github/workflows/e2e-samples-tests.yml

@@ -13,20 +13,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      # Setup Node.js and frontend first
-      - uses: actions/setup-node@v4
-        with:
-          node-version: lts/*
-
-      - name: Install frontend dependencies
-        working-directory: ./src/frontend
-        run: npm ci
-
-      - name: Build frontend
-        working-directory: ./src/frontend
-        run: npm run build
+      # Setup Node.js (needed for integrated frontend build in dotnet build)
+      - uses: voidzero-dev/setup-vp@v1
 
-      # Setup .NET and build backend (now with frontend assets available)
+      # Setup .NET and build backend (triggers frontend build automatically)
       - name: Setup .NET
         uses: actions/setup-dotnet@v4
         with:

.github/workflows/frontend-formatting-linting-checks.yml

@@ -19,23 +19,21 @@ jobs:
       - uses: actions/checkout@v4
 
       # Setup Node.js
-      - uses: actions/setup-node@v4
-        with:
-          node-version: lts/*
+      - uses: voidzero-dev/setup-vp@v1
 
       - name: Install dependencies
         working-directory: ./src/frontend
-        run: npm ci
+        run: vp install
 
       # Frontend code quality checks
       - name: Check code formatting
         working-directory: ./src/frontend
-        run: npm run format:check
+        run: vp fmt --check .
 
       - name: Check linting
         working-directory: ./src/frontend
-        run: npm run lint
+        run: vp lint .
 
       - name: Check frontend build
         working-directory: ./src/frontend
-        run: npm run build
+        run: vp build

.github/workflows/frontend-unit-tests.yml

@@ -13,14 +13,12 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - uses: actions/setup-node@v4
-        with:
-          node-version: lts/*
+      - uses: voidzero-dev/setup-vp@v1
 
       - name: Install dependencies
         working-directory: ./src/frontend
-        run: npm ci
+        run: vp install
 
       - name: Run unit tests
         working-directory: ./src/frontend
-        run: npm run test
+        run: vp test

AGENTS.md

@@ -31,14 +31,14 @@ public class MyView : ViewBase
 
 The topmost view in an Ivy application is called an [App](https://docs.ivy.app/onboarding/concepts/apps.md) and is decorated with the `[App]` attribute. The attribute uses **named constructor parameters** (lowercase):
 
-[App(title: "Customers", icon: Icons.Rocket, path: new[] { "CRM" })]
+[App(title: "Customers", icon: Icons.Rocket, group: new[] { "CRM" })]
 public class CustomersApp : ViewBase
 
 - `title` is optional — if omitted, it is derived from the class name (e.g. `CustomersApp` → "Customers").
 - `icon` uses the `Icons` enum — these are Lucide icons in PascalCase (e.g. `Icons.Link`, `Icons.Settings`, `Icons.Rocket`).
-- `path` groups the app in the navigation sidebar (e.g. `path: new[] { "Apps" }`).
-- There is no `group` or `chrome` parameter. Chrome is configured in `Program.cs` via `server.UseDefaultApp(typeof(MyApp))`.
-- Use **lowercase** parameter names (`icon:`, `path:`), NOT PascalCase property names (`Icon =`, `Path =`) — PascalCase causes CS0655.
+- `group` groups the app in the navigation sidebar (e.g. `group: new[] { "Apps" }`).
+- There is no `chrome` parameter. Chrome is configured in `Program.cs` via `server.UseDefaultApp(typeof(MyApp))`. Always ensure `server.AddAppsFromAssembly()` is called before `UseDefaultApp` — without it, `[App]`-attributed classes are not registered and the server throws at runtime.
+- Use **lowercase** parameter names (`icon:`, `group:`), NOT PascalCase property names (`Icon =`, `Group =`) — PascalCase causes CS0655.
 
 An app is built into a tree of widgets. This is what's rendered to the screen.
 
@@ -328,6 +328,10 @@ userNameState.ToTextInput().Required().MaxLength(50).Placeholder("Enter your nam
 - `DbContext` must never be injected directly! Always resolve `IDbContextFactory<T>` via `UseService` and create scoped instances with `CreateDbContextAsync()` inside query/mutation lambdas
 - **Nested layouts MUST use parentheses** — `Layout.Vertical() | (Layout.Horizontal() | child1 | child2)` — without parentheses, C# left-to-right `|` evaluation adds children to the outer layout, not the inner one. See the nested layout example in the Layouts section above.
 
+## CLI Commands
+
+Prefer using `ivy cli explain` for command discovery over MCP server tools as it provides a reliable, built-in structural breakdown.
+
 ## Further Reading
 
 [Forms](https://docs.ivy.app/onboarding/concepts/forms.md)

CONTRIBUTING.md

@@ -35,7 +35,8 @@ This project and everyone participating in it is governed by our [Code of Conduc
 ### Prerequisites
 
 - [.NET 10 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
-- [Node.js 22.12+ & npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm)
+- [Rust Toolchain](https://rustup.rs/) (latest stable via `rustup`)
+- [Node.js 22.12+ & vp CLI](https://github.com/voidzero-dev/vite-plus) (latest version)
 - **Ivy Console Tool** (for development):
 
   ```bash
@@ -78,31 +79,31 @@ Ivy Framework uses multiple testing approaches to ensure code quality:
 ### Unit Testing
 
 - **Backend (C#)**: Run `dotnet test` in the root directory
-- **Frontend (TypeScript)**: Run `npm run test` in the `src/frontend/` directory
+- **Frontend (TypeScript)**: Run `vp test` in the `src/frontend/` directory
 
 ### End-to-End Testing
 
-E2E tests are written using Playwright and are located in `src/frontend/e2e/`. We provide npm scripts for running these tests:
+E2E tests are written using Playwright and are located in `src/frontend/e2e/`. We provide `vp` scripts for running these tests:
 
 ```bash
 # Run all E2E tests
-npm run e2e
+vp run e2e
 
 # Run only Ivy.Docs E2E tests
-npm run e2e:docs
+vp run e2e:docs
 
 # Run only Ivy.Samples E2E tests
-npm run e2e:samples
+vp run e2e:samples
 ```
 
-**Important**: Always use the npm scripts (`npm run e2e*`) instead of `npx playwright test` to ensure consistent usage of the locally installed Playwright version and avoid version conflicts.
+**Important**: Always use the `vp` scripts (`vp run e2e*`) instead of `npx playwright test` to ensure consistent usage of the locally installed Playwright version and avoid version conflicts.
 
 Additional Playwright options can be passed after `--`:
 
 ```bash
-npm run e2e -- --headed  # Run tests in headed mode
-npm run e2e -- --debug   # Run tests in debug mode
-npm run e2e:samples -- --project=chromium  # Run samples tests in Chrome only
+vp run e2e -- --headed  # Run tests in headed mode
+vp run e2e -- --debug   # Run tests in debug mode
+vp run e2e:samples -- --project=chromium  # Run samples tests in Chrome only
 ```
 
 ## Contributing Guidelines
@@ -260,15 +261,15 @@ Before submitting your code, ensure it follows the project's linting and formatt
 
 #### Frontend (TypeScript/React)
 
-- Use `npm run lint:fix` to automatically fix ESLint issues
-- Use `npm run format` to format code with Prettier
+- Use `vp lint --fix .` to automatically fix ESLint issues
+- Use `vp fmt .` to format code with Oxfmt
 - These commands should be run from the `src/frontend/` directory
 
 #### Pre-commit Hooks
 
 The project uses pre-commit hooks that will automatically run linting and formatting on staged files. Make sure your code passes these checks before committing. More details how pre-commit hooks are being set up can be found in `src/frontend/README.md`
 
-TL;DR, if you have run `npm install` in the `src/frontend`, most likely all pre-commit hooks will be working for you, that cover linting and formatting for Ivy-Framework.
+TL;DR, if you have run `vp install` in the `src/frontend`, most likely all pre-commit hooks will be working for you, that cover linting and formatting for Ivy-Framework.
 
 ### C# Guidelines
 
@@ -336,15 +337,15 @@ dotnet test src/Ivy.Test
 
 # Run frontend unit tests
 cd src/frontend
-npm run test
+vp test
 
 # Run all frontend E2E tests
 cd src/frontend
-npm run e2e
+vp run e2e
 
 # Run specific E2E test suites
-npm run e2e:docs      # Ivy.Docs tests only
-npm run e2e:samples   # Ivy.Samples tests only
+vp run e2e:docs      # Ivy.Docs tests only
+vp run e2e:samples   # Ivy.Samples tests only
 ```
 
 ### Writing Tests