Verify React.lazy route splitting from the Vite build output, not just the source
To confirm a route-level React.lazy split really keeps heavy map/WebGL code (deck.gl, Google Maps loader) off the first load, run vite build and inspect dist/index.html: only the entry script and its modulepreload links load up front. The lazy pages and their dependencies show up in the entry chunk's __vite__mapDeps list, which means they are dynamic imports, fetched only when the route opens. A grep of the entry chunk for the package names should return 0. When reviewing a PR whose branch is behind main, a red test the PR doesn't touch is often already fixed on main: merge the branch onto current main in a scratch worktree and rerun there before blaming the PR. Tests that reject /tmp/ paths in output will fail if that scratch worktree lives under /tmp, so put it elsewhere or compare against plain main in the same location.