Vite Plugin

The official Vite plugin gives you a Vite-native dev server with SSR rendering and automatic island entry generation.

# Setup

// vite.config.ts
import { defineConfig } from "vite";
import { elurJsKit } from "@elurjs/kit/vite";

export default defineConfig({
  plugins: [
    elurJsKit({
      appDir: "src/app",
      islandsDir: "src/islands",
      contentDir: "src/content",
      generatedEntry: ".elur/entry-client.ts",
      clientEntry: "/_elur/entry-client.js",
      lang: "en",
    }),
  ],
});

Then run:

npx vite

# Options

# ElurJsKitViteOptions

# What the plugin does

# Dev mode

• Scans src/app/ for routes, layouts, actions, and error pages
• Generates .elur/entry-client.ts from scanned islands
• Renders every page via SSR on the Vite dev server
• Serves the /__elur/render endpoint (HTML or JSON) for SPA navigation
• Serves the /__elur/actions endpoint for server actions
• Wires up the content layer root (setContentRoot)
• Loads src/middleware.ts if it exists
• Provides HMR for routes, actions, loaders, islands, and .md content files

# Build mode

In production builds, the plugin works alongside elur-kit build to generate static HTML and the client bundle.

# Attribute interpolation

The plugin includes an interpolation transform that rewrites partial attribute interpolations:

// You write:
html`<a href="/blog/${slug}">Read</a>`

// The plugin transforms it to:
html`<a href=${() => `/blog/${slug}`}>Read</a>`

This works in both src/app/ and src/islands/ files, so you can write natural href attributes without manual workarounds.

# Client bundle

If you have a vite.client.config.ts file, the client hydration bundle is built automatically during elur-kit build and elur-kit dev. You can also pass an explicit config with --client-config <path>.

# Content layer HMR

When a .md file in src/content/ changes, the plugin clears the content cache so the next request picks up the updated content. No server restart is needed.

# Middleware integration

The plugin loads src/middleware.ts on startup and runs it before every request, matching the behavior of elur-kit start and all deployment adapters.