packages/react/src/stream/vite.ts (1)

1-4: Optional: consolidate imports from unhead/stream/vite.

Minor — StreamingPluginOptions (type) and createStreamingVitePlugin (value) could share a single import { createStreamingVitePlugin, type StreamingPluginOptions } from 'unhead/stream/vite' statement.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/react/src/stream/vite.ts` around lines 1 - 4, Consolidate the two
imports from 'unhead/stream/vite' by merging the separate type import and value
import into a single statement that imports both createStreamingVitePlugin and
the type StreamingPluginOptions together; update the existing import occurrences
for StreamingPluginOptions and createStreamingVitePlugin to use a single
combined import line so there are no duplicate module specifiers.

packages/svelte/src/stream/vite.ts (1)

1-4: Optional: consolidate imports from unhead/stream/vite.

Same as React — the type import on line 1 and value import on line 4 could be merged into one statement using inline type specifiers.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/svelte/src/stream/vite.ts` around lines 1 - 4, Merge the two imports
from 'unhead/stream/vite' into a single import statement that uses inline type
specifiers: keep StreamingPluginOptions as a type and createStreamingVitePlugin
as a value in the same import. Update the import that currently references
StreamingPluginOptions and the separate createStreamingVitePlugin import so both
symbols are imported together (e.g., using "import { StreamingPluginOptions,
createStreamingVitePlugin } from 'unhead/stream/vite'" with
StreamingPluginOptions marked as a type), leaving the other imports
(MagicString, parseAndWalk) unchanged.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

packages/unhead/src/stream/unplugin.ts (2)

12-34: ⚠️ Potential issue | 🟠 Major

Use one SSR detector for both load and transform.

load still only reads the mutable ssr closure, so Vite dev/custom server environments can receive browser code for the virtual modules. Also include this.environment.config.consumer === 'server' for Vite 6+ custom environment names, and add an explicit options.ssr fallback for Rollup/direct usage. See Vite SSR hook options and Vite’s environment migration docs: https://vite.dev/guide/ssr#ssr-specific-plugin-logic, https://vite.dev/changes/this-environment-in-hooks.

🔧 Proposed fix

 export interface StreamingPluginOptions {
   /** Framework package e.g. '@unhead/vue' */
   framework: string
@@
    * `@default` 'async'
    */
   mode?: 'async' | 'inline' | 'module'
+  /** Explicit SSR fallback for bundlers/tests that do not provide a hook-level SSR signal. */
+  ssr?: boolean
 }
@@
 export function buildStreamingPluginOptions(options: StreamingPluginOptions): UnpluginOptions {
   const { framework, name, mode = 'async' } = options
   let ssr = false
+
+  const isSsrContext = (ctx?: any, opts?: { ssr?: boolean }) => {
+    const environment = ctx?.environment
+    return environment?.config?.consumer === 'server'
+      || environment?.name === 'ssr'
+      || environment?.name === 'server'
+      || opts?.ssr === true
+      || options.ssr === true
+      || ssr
+  }
@@
     load: {
       filter: { id: RESOLVED_RE },
-      handler(id) {
+      handler(this: any, id: string, opts?: { ssr?: boolean }) {
+        const isSSR = isSsrContext(this, opts)
         if (id === RESOLVED_ID) {
-          if (ssr)
+          if (isSSR)
             return { code: 'export {}' }
@@
         }
         if (id === RESOLVED_IIFE_ID) {
-          if (ssr)
+          if (isSSR)
             return { code: '' }
@@
             handler(this: any, code: string, id: string, opts?: { ssr?: boolean }) {
-              // Vite v6+ dev mode exposes environment per-transform call (one plugin
-              // instance, two environments). Fall back to the options.ssr flag
-              // (vite <=5 and tests), then the bundler-hook closure for
-              // vite build (separate instances per build) and webpack/rspack.
-              const envName = this?.environment?.name
-              const isSSR = envName === 'ssr' || envName === 'server' || opts?.ssr === true || ssr
+              const isSSR = isSsrContext(this, opts)
               return options.transform!(code, id, { ssr: isSSR })
             },

Also applies to: 82-100, 107-114

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/unhead/src/stream/unplugin.ts` around lines 12 - 34, Create a single
SSR detection helper and use it from both the load and transform hooks: detect
SSR by checking the existing mutable ssr closure (if defined and truthy), OR
this.environment.config.consumer === 'server' (for Vite 6+ custom envs), OR the
options?.ssr boolean fallback (for Rollup/direct API usage); replace the current
ad-hoc checks in load and transform so both call this helper to decide whether
to return browser or server code and ensure load no longer reads only the
mutable ssr closure.

---

136-160: ⚠️ Potential issue | 🟠 Major

Run virtual-module HTML injection before Vite processes HTML scripts.

These injected scripts reference /${VIRTUAL_IIFE_ID} and /${VIRTUAL_CLIENT_ID}. Vite’s transformIndexHtml docs reserve order: 'pre' for injected scripts that must pass through the plugin pipeline; otherwise production HTML can retain raw /virtual: URLs. See https://vite.dev/guide/api-plugin#transformindexhtml.

🔧 Proposed fix

-      transformIndexHtml() {
-        if (mode === 'inline') {
-          if (!iifeCode)
-            throw new Error('[unhead] Streaming IIFE not built. Run `pnpm build` in packages/unhead first.')
-          return [{
-            tag: 'script',
-            children: iifeCode,
-            injectTo: 'head-prepend',
-          }]
-        }
-
-        if (mode === 'async') {
-          return [{
-            tag: 'script',
-            attrs: { async: true, src: `/${VIRTUAL_IIFE_ID}` },
-            injectTo: 'head-prepend',
-          }]
-        }
-
-        return [{
-          tag: 'script',
-          children: `import("/${VIRTUAL_CLIENT_ID}")`,
-          injectTo: 'head-prepend',
-        }]
+      transformIndexHtml: {
+        order: 'pre',
+        handler() {
+          if (mode === 'inline') {
+            if (!iifeCode)
+              throw new Error('[unhead] Streaming IIFE not built. Run `pnpm build` in packages/unhead first.')
+            return [{
+              tag: 'script',
+              children: iifeCode,
+              injectTo: 'head-prepend',
+            }]
+          }
+
+          if (mode === 'async') {
+            return [{
+              tag: 'script',
+              attrs: { async: true, src: `/${VIRTUAL_IIFE_ID}` },
+              injectTo: 'head-prepend',
+            }]
+          }
+
+          return [{
+            tag: 'script',
+            children: `import("/${VIRTUAL_CLIENT_ID}")`,
+            injectTo: 'head-prepend',
+          }]
+        },
       },

Run this read-only check for direct test/call-site invocations that need to switch to .handler(...) after this shape change:

#!/bin/bash
rg -nP '\.transformIndexHtml\s*\(' --type ts -C3

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/unhead/src/stream/unplugin.ts` around lines 136 - 160, The injected
script objects returned from transformIndexHtml must be marked to run before
Vite processes HTML scripts so virtual-module URLs are transformed; update the
three return objects in transformIndexHtml (the inline iifeCode branch, the
async branch that uses VIRTUAL_IIFE_ID, and the default branch that imports
VIRTUAL_CLIENT_ID) to include order: 'pre' on each injected script descriptor;
also scan for any direct calls to transformIndexHtml and update them to use the
new handler shape (call .handler(...) where needed) so callers match the changed
plugin API.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes