charlie: port main preview deploy + asset path fixes to next/v3

[charliecreates]

Target branch
All PRs must branch from next/v3 and target base next/v3 (not main).

Context
From the reconciliation report in #379, several post-merge-base main fixes around preview/deploy builds and preview static assets are not present in next/v3.

This bucket should also coordinate with (and likely subsume) the existing Windows-focused tracking issue #366.

Scope (files/areas)

• packages/jsx-email/src/cli/commands/preview.ts
• packages/jsx-email/src/cli/vite-static.ts
• test/cli/** (add/port the targeted preview build-path test)

Tasks

1. Port the main fix that normalizes glob paths passed to globby() for preview static assets:
   • In packages/jsx-email/src/cli/vite-static.ts, apply Vite-style normalizePath() to each configured glob before calling globby().
   • (Evidence on main: cb00aa67 touched packages/jsx-email/src/cli/vite-static.mts.)
2. Align email preview --build-path behavior with main:
   • Allow relative --build-path values (resolve against the original CWD).
   • Keep absolute paths working unchanged.
   • Update help text so it no longer claims “absolute only”.
   • (Evidence on main: b7eaa939 in packages/jsx-email/src/cli/commands/preview.mts.)
3. Port the main fix that removes Rollup externals for deployable preview builds:
   • In buildDeployable’s Vite config, do not mark react/jsx-runtime as external.
   • (Evidence on main: 0954a3d3 in packages/jsx-email/src/cli/commands/preview.mts.)
4. Port/restore Windows drive-letter handling used by main for Vite root/build-path interactions (if still applicable in next/v3’s structure).
5. Add/port the targeted CLI regression test from main:
   • test/cli/preview-build-path.test.ts (adapt as needed for next/v3)

Acceptance criteria (done when)

• email preview ./templates --build-path ./.deploy works (writes output under the resolved path) and does not break absolute paths.
• Preview static assets are served correctly when globs contain Windows path separators.
• Deployable preview build no longer relies on react/jsx-runtime being externalized.
• The new/ported CLI test passes.

Verification

# CLI tests
$ FORCE_COLOR=1 moon test-cli:test.run

# Preview-related unit tests
$ FORCE_COLOR=1 moon jsx-email:test

# Optional (if/when smoke is working again)
$ moon test-smoke:run

Refs #379.

[charliecreates]

Expand this to see my work.

• Scanned apps/preview/app/src/layouts/Shell.tsx and apps/preview/app/src/components/sidebar.tsx to confirm Shell imports { Header, Sidebar } from ../components/Sidebar while the on-disk component is sidebar.tsx exporting Sidebar and Header, and sidebar.tsx imports Logo and Separator from ./logo and ./Separator respectively.
• Listed apps/preview/app/src/components and apps/preview/app/src/components/ui to verify actual file casing (logo.tsx, sidebar.tsx, Separator.tsx, etc.) so that imports in Shell.tsx and the built preview app align with case-sensitive module resolution.
• Searched under apps/preview/app/src for imports referencing components/Sidebar, components/sidebar, ./Logo, and ./logo to pinpoint the mismatched import in Shell.tsx and confirm sidebar.tsx already correctly imports Logo from ./Logo in main, narrowing the failure to build-time path/casing behavior in next/v3.
• Inspected the tail of apps/preview/app/src/components/sidebar.tsx to verify export const Sidebar and export const Header along with their use of Logo and Separator, confirming symbol exports are correct and that only import paths/casing are suspect for the preview build.
• Opened apps/preview/app/src/components/logo.tsx to confirm it exports Logo and matches the intended import usage, ruling out missing exports as a root cause for the CLI regression and keeping focus on Vite/Rollup resolution.
• Updated apps/preview/app/src/components/sidebar.tsx to import Logo from ./logo instead of ./Logo so the source app matches the lowercase logo.tsx filename used on disk, then rebuilt via pnpm exec moon run jsx-email:build to refresh packages/jsx-email/dist/preview.
• Re-ran the CLI Vitest suite with pnpm exec vitest --config ../../shared/vitest.config.ts under test/cli, confirming all tests including test/cli/preview-build-path.test.ts now pass with the updated packages/jsx-email/src/cli/commands/preview.ts and packages/jsx-email/src/cli/vite-static.ts behavior on branch ai-381-charlie-port-main-preview-deploy-asset-path.
• Ran git diff --name-only to verify the scoped changes are limited to apps/preview/app/src/components/sidebar.tsx, apps/preview/app/src/layouts/Shell.tsx, packages/jsx-email/src/cli/commands/preview.ts, packages/jsx-email/src/cli/vite-static.ts, and test/cli/preview-build-path.test.ts, matching the intended surface for Issue #381.
• Ran pnpm exec moon run repo:lint to satisfy the PR template’s repo-wide lint requirement, noted only warnings (no errors) plus auto-written docs, and then used git restore on docs/components/graph.md, docs/core/compile.md, and docs/core/plugins.md so no unrelated docs diffs are included in this branch.
• Opened PR #387 from ai-381-charlie-port-main-preview-deploy-asset-path to next/v3 with a filled-out template, linked issues (charlie: port main preview deploy + asset path fixes to next/v3 #381, charlie: port windows asset path fix to v3 #366, charlie: reconcile main with next/v3 #379), and a verification section describing the repo:lint, jsx-email:build, Prettier, oxlint, and Vitest runs for packages/jsx-email and test/cli.

[charliecreates]

Opened PR #387 against next/v3: #387

It ports the main preview/deploy + asset-path fixes into next/v3 (and includes the preview --build-path regression test), plus a small preview-app import-casing fix needed for deploy builds to work on Linux.

Changes

• packages/jsx-email/src/cli/vite-static.ts: normalize glob patterns with Vite’s normalizePath() before passing to globby(), so Windows separators don’t break static asset serving.
• packages/jsx-email/src/cli/commands/preview.ts:
  • resolve relative --build-path against originalCwd (absolute paths unchanged)
  • update help text (no longer “absolute only”)
  • remove react/jsx-runtime from Rollup externals for deployable preview builds
  • restore Windows drive-letter guard for Vite root vs temp dir
• apps/preview/app: fix case-sensitive imports (Sidebar/Logo) so deploy builds work on case-sensitive filesystems.
• test/cli/preview-build-path.test.ts: new CLI regression test (ported from main).

Verification

# Lint (0 errors; 31 warnings)
$ pnpm exec moon run repo:lint
# Note: this task auto-writes docs; unrelated rewrites were discarded.

# Build
$ pnpm exec moon run jsx-email:build --updateCache

# Prettier (changed files): OK
$ pnpm prettier --check apps/preview/app/src/components/sidebar.tsx apps/preview/app/src/layouts/Shell.tsx packages/jsx-email/src/cli/commands/preview.ts packages/jsx-email/src/cli/vite-static.ts test/cli/preview-build-path.test.ts

# OXLint (changed files): 0 errors (1 warning)
$ pnpm oxlint apps/preview/app/src/components/sidebar.tsx apps/preview/app/src/layouts/Shell.tsx packages/jsx-email/src/cli/commands/preview.ts packages/jsx-email/src/cli/vite-static.ts test/cli/preview-build-path.test.ts

# Vitest (jsx-email): 41 files; 184 tests passed
$ cd packages/jsx-email && mise exec node@20.19.0 -- env FORCE_COLOR=1 pnpm exec vitest --config ../../shared/vitest.config.ts

# Vitest (CLI): 4 files; 4 tests passed
$ cd test/cli && mise exec node@20.19.0 -- env FORCE_COLOR=1 pnpm exec vitest --config ../../shared/vitest.config.ts

PR includes resolves #381 and resolves #366 in the body (per the issue’s note that this work likely subsumes #366).