charlie: port windows asset path fix to v3

[shellscape]

Please port the fix from #365 onto the next/v3 branch. Make sure the PR is opened against the next/v3 branch.

[charliecreates]

Expand this to see my work.

• Reviewed the Windows path handling changes in packages/core/src/assetPath.ts and related utilities from PR #365 and applied the equivalent logic on next/v3 without impacting v3-specific APIs.
• Confirmed packages/jsx-email/src/cli/vite-static.ts is the correct v3 analogue of vite-static.mts and re-applied the normalizePath behavior so globby now consumes paths.map((path) => normalizePath(path)) with normalizePath imported from vite.
• Verified existing tests and type checks for assetPath and the CLI on next/v3 still behave as before, with pnpm moon run jsx-email:tsc failing only on the known TS2717 'jsx-email-cond' duplicate declaration in src/components/conditional.tsx.
• Ran pnpm moon run plugin-inline:build plugin-minify:build plugin-pretty:build and pnpm moon run jsx-email:build, confirming all builds (including the updated vite-static.ts) succeed with exit code 0.
• Ran pnpm moon run repo:lint and confirmed lint passes with only pre-existing warnings, indicating the Windows path and CLI tweaks didn’t introduce new lint issues.
• Re-ran pnpm moon run jsx-email:tsc after the latest vite-static.ts adjustment and confirmed the TypeScript output is unchanged from earlier runs, showing the normalization change is type-safe on v3.
• Checked the working tree with git status -sb and git diff --stat to confirm the v3 port is scoped to packages/jsx-email/src/cli/vite-static.ts with a 2-line insertion/2-line deletion diff.
• Committed the change as fix(jsx-email): normalize preview asset globs on v3, which ran staged-file hooks (oxlint --format stylish --fix and prettier --write) successfully before finalizing the commit.
• Pushed the feature branch ai-366-charlie-port-windows-asset-path-fix-to-v3 to origin so the next/v3-targeted bugfix PR for the email preview Windows asset paths can be opened on GitHub.
• Attempted to create a PR titled fix(jsx-email): normalize globby paths for preview (v3) against next/v3 with a full verification section and resolves #366 in the body, but the shell-quoted gh pr create command failed due to a mismatched quote in the here-doc body and needs a simpler quoting strategy or manual creation in the GitHub UI.

[charliecreates]

Opened #367 porting the Windows preview asset path fix from #365 onto next/v3 with a minimal CLI-only change.

Changes

• Based ai-366-charlie-port-windows-asset-path-fix-to-v3 on origin/next/v3 and targeted the PR’s base branch to next/v3.
• Updated packages/jsx-email/src/cli/vite-static.ts:
  • Changed the Vite import from types-only to include the runtime helper:

    import { globby } from 'globby';
    import mime from 'mime-types';
    import { normalizePath, type PluginOption, type ViteDevServer } from 'vite';

  • Normalized the configured static asset paths before passing them to globby, mirroring the fix on main:

    const middleware = async (params: MiddlwareParams) => {
      const { options, server } = params;
      const { paths } = options;
      const files = await globby(paths.map((path) => normalizePath(path)));
      // ...
    };

• This matches the behavior from packages/jsx-email/src/cli/vite-static.mts on main, so on Windows the email preview static middleware now treats --assets globs as POSIX-style paths that globby can match, while behavior on non-Windows platforms stays the same.
• No other files (tests, configs, lockfile, etc.) were changed; git diff --stat origin/next/v3...HEAD shows only the one touched file above.

Verification

# Build plugins used by jsx-email
$ pnpm moon run plugin-inline:build plugin-minify:build plugin-pretty:build

# Build jsx-email (next/v3)
$ pnpm moon run jsx-email:build

# Lint (warnings only; no errors)
$ pnpm moon run repo:lint

# jsx-email tests (next/v3 config)
$ pnpm moon run jsx-email:test

# TypeScript: jsx-email (preexisting failure)
$ pnpm moon run jsx-email:tsc

• Plugin builds all succeeded (plugin-inline:build, plugin-minify:build, plugin-pretty:build).
• jsx-email:build completed successfully.
• repo:lint completed with 31 existing warnings in apps/docs/tests but no errors; nothing related to vite-static.ts.
• jsx-email:test passed: 46 test files, 190 tests.
• jsx-email:tsc fails with a preexisting TS2717 error in packages/jsx-email/src/components/conditional.tsx about duplicate 'jsx-email-cond' declarations.
  • This error reproduces on an unmodified origin/next/v3 checkout (before applying the vite-static.ts change) and remains unchanged after the port.

Notes

• The automated self-review surfaced a number of maintainability items (pnpm workspace flags, shared tsconfig changes, CLI test reshaping, Playwright/diffable-html versions, smoke snapshots, etc.) that are not part of this branch’s diff; they come from prior next/v3 alignment work (e.g. chore(charlie): align next/v3 core correctness with main for compile, preview, config #355, feat(charlie): align next/v3 CLI --use-preview-props behavior with main #358, fix(create-mail): add react-dom to scaffold devDeps #359, chore(charlie): align next/v3 Raw and Conditional pipeline with main #360, chore(charlie): align next/v3 docs/playbooks with main for Raw, Conditional, tests #361).
• To keep this PR tightly scoped to Issue charlie: port windows asset path fix to v3 #366, I only touched packages/jsx-email/src/cli/vite-static.ts to port the Windows asset path fix from fix(jsx-email): normalize globby paths for preview command #365 and left those broader repo-level/tooling changes as-is.