From 51aff8cc8747d31b7755ea639493f640562858b0 Mon Sep 17 00:00:00 2001 From: Padreug Date: Sat, 2 May 2026 14:20:48 +0200 Subject: [PATCH] fix(dev): pin hub port to 5173 with strictPort The 7 standalone vite configs had server.port + strictPort: true since commit 9a1e5e3, but the hub config was left on the default auto-incrementing 5173. When something briefly held 5173 (an orphaned vite process from a crashed restart, an ENOENT during concurrent dep optimization, etc.) the hub silently drifted to 5174. The browser's cached SW kept loading the page from localhost:5173, all in-page asset fetches died with ERR_CONNECTION_REFUSED, and chakra navigation appeared broken. Pinning the hub the same way the standalones are pinned eliminates that drift. If 5173 is genuinely held when dev:all starts, vite will fail loud (and the user can free the port) instead of moving the hub silently. Co-Authored-By: Claude Opus 4.7 (1M context) --- vite.config.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/vite.config.ts b/vite.config.ts index 81d6e97..716dad6 100644 --- a/vite.config.ts +++ b/vite.config.ts @@ -9,6 +9,10 @@ import { visualizer } from 'rollup-plugin-visualizer' // https://vite.dev/config/ export default defineConfig(({ mode }) => ({ + server: { + port: 5173, + strictPort: true, + }, plugins: [ vue(), tailwindcss(),