mirror of
https://github.com/hanzoai/base.git
synced 2026-10-21 03:41:50 +00:00
zeekayandHanzo Dev
53b538f2fb
Every other package in this admin was already on its latest published version; vite was two majors behind at 6.4.3. Both plugins support 8 at their latest (@vitejs/plugin-react 6.0.5 peers vite ^8.0.0, router-plugin 1.168.23 peers >=8.0.0), so the pin was the only thing keeping it there. `esbuild` was a direct devDependency that nothing imported: no source file references it and no plugin here peers on it — router-plugin's peer list is rsbuild/vite/solid/webpack/react-router. It only surfaced as a problem because vite 8 peers esbuild ^0.27||^0.28 and 0.25 tripped it, which is how a vestigial dep announces itself. Removing it is what silenced the warning; bumping it would have kept an unused package on the list. `build.rollupOptions.output.manualChunks: undefined` set a default to its own default. Removing it produces byte-identical output (same content hashes), and under rolldown the option is spelled elsewhere anyway, so it was config that could only mislead. Rolldown does the same work in a fraction of the time and ships less of it: 7.9s -> 1.3s, 871 kB -> 836 kB (gzip 269 -> 254). Verified the bundle, not just the build — the whole point of smoke.mjs is that a green build says nothing about what renders, and a bundler swap is exactly the change that could quietly break it. All 19 routes paint, every token resolves, no utility-class residue, no unprobed control, overlays open, confirm dialog measures 384. pnpm build 0 (vite v8.2.0, built in 1.34s) · pnpm smoke SMOKE OK 0 · CGO_ENABLED=0 go build 0 · go test -count=1 ./ui-react/... ./apis/... ok 144.5s Co-authored-by: Hanzo Dev <[email protected]>
