Kez/kez-chat/web/vite.config.ts

import { execSync } from "node:child_process";
import { existsSync, readFileSync } from "node:fs";
import { defineConfig } from "vite";
import { svelte } from "@sveltejs/vite-plugin-svelte";
import tailwindcss from "@tailwindcss/vite";
import { VitePWA } from "vite-plugin-pwa";

// Build-time identity: short git SHA + ISO date. Surfaced in the footer
// as "kez-chat <sha>" so users can eyeball which build they're on (handy
// when verifying that a deploy actually landed instead of being cached).
//
// Resolution order, so it works both locally (with .git) and in the
// Docker build on the remote (no .git copied):
//   1. process.env.BUILD_SHA              — set by deploy script
//   2. ./BUILD_SHA file in this dir       — set by deploy script
//   3. `git rev-parse --short HEAD`       — local dev
//   4. "dev"                              — give up
const BUILD_SHA = (() => {
  if (process.env.BUILD_SHA) return process.env.BUILD_SHA.trim();
  if (existsSync("./BUILD_SHA")) {
    return readFileSync("./BUILD_SHA", "utf-8").trim();
  }
  try {
    return execSync("git rev-parse --short HEAD").toString().trim();
  } catch {
    return "dev";
  }
})();
const BUILD_TIME = new Date().toISOString();

export default defineConfig({
  define: {
    __BUILD_SHA__: JSON.stringify(BUILD_SHA),
    __BUILD_TIME__: JSON.stringify(BUILD_TIME),
  },
  plugins: [
    svelte(),
    tailwindcss(),
    VitePWA({
      // Auto-update: a new SW activates on next page load. No "click to
      // update" prompt — chat needs to stay fresh and we don't want users
      // stuck on an old build.
      registerType: "autoUpdate",
      injectRegister: "auto",
      // We need a custom Service Worker so we can handle `push` and
      // `notificationclick` events. `injectManifest` keeps the workbox
      // precache list autogenerated but lets us own the SW source.
      strategies: "injectManifest",
      srcDir: "src",
      filename: "sw.ts",
      injectManifest: {
        // zstd wasm is ~350 KB; raise the per-file cap so the precache
        // doesn't silently skip it.
        maximumFileSizeToCacheInBytes: 5 * 1024 * 1024,
        globPatterns: ["**/*.{js,css,html,svg,png,ico,wasm}"],
      },
      manifest: {
        name: "kez-chat",
        short_name: "kez-chat",
        description:
          "End-to-end encrypted chat on top of KEZ — portable cross-app identity.",
        start_url: "/",
        scope: "/",
        display: "standalone",
        background_color: "#0b0c0e",
        theme_color: "#0b0c0e",
        categories: ["social", "communication"],
        icons: [
          { src: "pwa-64x64.png", sizes: "64x64", type: "image/png" },
          { src: "pwa-192x192.png", sizes: "192x192", type: "image/png" },
          { src: "pwa-512x512.png", sizes: "512x512", type: "image/png" },
          {
            src: "maskable-icon-512x512.png",
            sizes: "512x512",
            type: "image/png",
            purpose: "maskable",
          },
        ],
      },
      // No `workbox: {...}` here — that key only applies in
      // `generateSW` mode. In injectManifest mode, the SW source itself
      // (src/sw.ts) handles caching strategies + push events.
      devOptions: {
        enabled: false,
      },
    }),
  ],
  server: {
    // For dev: proxy API calls to the locally-running chat-server.
    // The deployed SPA (served by the same chat-server) doesn't need this.
    proxy: {
      "/v1": "http://localhost:6969",
      "/internal": "http://localhost:6969",
      "/.well-known": "http://localhost:6969",
    },
  },
  build: {
    outDir: "dist",
    emptyOutDir: true,
  },
});