Fresh 2 + Vite keeps rebuilding on Windows

[FredslundMagnus]

Fresh 2 + Vite keeps rebuilding on Windows, when some tempory files are changed and I cannot disable it:

import { defineConfig } from "vite";
import { fresh } from "@fresh/plugin-vite";
import tailwindcss from "@tailwindcss/vite";

export default defineConfig({
  plugins: [
    fresh(),
    tailwindcss(),
  ],
  server: {
    watch: {
      // Don't watch test files, temp files, or hidden files during development
      // to prevent dev server crashes
      ignored: [
        "**\\*_test.ts*",
        "**/*_test.ts*",
        "**\\*.test.ts*",
        "**/*.test.ts*",
        "**\\*.tmp.*",
        "**/*.tmp.*",
        "**\\*.timestamp-*",
        "**/*.timestamp-*",
        "**\\.*",
        "**/.*",
        "**\\encrypted\\**",
        "**/encrypted/**",
        "**\\kv\\**",
        "**/kv/**",
        "vite.config.*",
        "encrypted\\kv\\main-shm",
        "encrypted/kv/main-shm",
        "encrypted\\kv\\main-wal",
        "encrypted/kv/main-wal",
        "node_modules\\**",
        "node_modules/**",
        "**/*",
        "**\\*",
        "**",
        "*",
      ],
    },
  },
});

I also tried:

import { defineConfig } from "vite";
import { fresh } from "@fresh/plugin-vite";
import tailwindcss from "@tailwindcss/vite";

export default defineConfig({
  plugins: [
    fresh(),
    tailwindcss(),
  ],
  server: {
    watch: null,
  },
});

I got it working on wsl, and I've tried with both path type \ and /, but it keeps rebuilding.

[bartlomieju]

The root cause appears to be in packages/plugin-vite/src/plugins/server_snapshot.ts — the watcher.on("all", ...) handler sends a fresh:reload WebSocket message unconditionally on every file change event (line 124), regardless of whether the file is relevant to the app:

viteServer.watcher.on("all", (ev, filePath) => {
  // ... checks for island files (returns early)
  // ... checks for route add/unlink (invalidates module)

  // This fires for EVERY file change with no guard:
  viteServer.ws.send("fresh:reload");
});

On Windows, file system watchers commonly emit duplicate/spurious events due to delayed file close semantics and journaling. Combined with frequently-written files like Deno KV (main-shm, main-wal), each write triggers a full page reload. Setting server.watch.ignored or server.watch: null doesn't help because Fresh hooks directly into Vite's chokidar watcher instance — by the time Fresh's handler runs, the ignore config doesn't filter these events (especially with Windows path separator mismatches \\ vs /).

This works fine on WSL because Linux's inotify emits cleaner, deduplicated events.

The fix would be to either gate the fresh:reload so it only fires for files actually used by the server (SSR module graph check), or remove the unconditional send entirely and only reload on route file add/unlink where it's already handled above.