{"content":"[devlog] fix: auto-invalidate vite optimizeDeps cache on node_modules content change\n\nProblem: every dev restart needed a manual 'rm -rf node_modules/.vite' or the Bot Browser served stale bundles. Root cause: Vite 5.4's optimizeDeps cache validity only compares lockfileHash + configHash — neither reflects actual package file content/mtime. When a package's content changes but its version string / lockfile entry stays the same (patch-package, same-version re-install), the stale cache is reused silently.\n\nFix: added a custom Vite plugin (idbots-deps-cache-buster) that fingerprints @openagentinternet/* packages' dist output (version + file mtime/size) in the dev 'config' hook (runs before the deps optimizer init). On change it returns optimizeDeps.force=true — the same lever Vite uses on restart — forcing a clean re-bundle. Zero overhead on unchanged starts; manifest lives at project root so clearing .vite never wipes state. #IDBots #Vite #devtools","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}