| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .prettierrc.mjs | ||
| bun.lock | ||
| index.html | ||
| package.json | ||
| postcss.config.js | ||
| tailwind.config.js | ||
| vercel.json | ||
| vite.config.js |
Home was unexpectedly loading the `visactor-*.js` bundle on first paint. This happened because the Vite manualChunks entry created a standalone vendor chunk for VisActor, which Vite then preloaded on the initial route. What’s changed - Removed `visactor` from `build.rollupOptions.output.manualChunks` in `web/vite.config.js`. Why - Prevents VisActor from being preloaded on the Home page. - Restores the intended behavior: VisActor loads only when the Dashboard (data analytics) is visited. Impact - Smaller initial payload and fewer network requests on Home. - No functional changes to charts; loading behavior is now route-driven. Test plan - Build the app: `cd web && npm run build`. - Open the preview and visit `/`: ensure no `visactor-*.js` is requested. - Navigate to `/console` (Dashboard): ensure `visactor-*.js` loads as expected.
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| public | Loading commit data... | |
| src | Loading commit data... | |
| .eslintrc.cjs | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .prettierrc.mjs | Loading commit data... | |
| bun.lock | Loading commit data... | |
| index.html | Loading commit data... | |
| package.json | Loading commit data... | |
| postcss.config.js | Loading commit data... | |
| tailwind.config.js | Loading commit data... | |
| vercel.json | Loading commit data... | |
| vite.config.js | Loading commit data... |