Use Next.js conventions in bundle analyzer UI (#98780)
Use the App Router error boundary and `next-themes` provider instead of custom client-side equivalents. Persist environment, file type, and debounced file search filters in URL search parameters so analyzer views can be shared. Remove the incompatible `next start` script from the statically exported app. ## What? - Add an App Router `error.tsx` boundary with segment reset support - Replace the inline theme bootstrap script with `next-themes` - Store analyzer filters and file search in URL search parameters - Remove the static export's `next start` script ## Why? Use the framework's existing error, theme, and navigation integration while keeping the analyzer's static export deployment model. ## How was it tested? - `pnpm --filter=@next/bundle-analyzer-ui exec tsc --noEmit` - `pnpm --filter=@next/bundle-analyzer-ui lint` - `pnpm --filter=@next/bundle-analyzer-ui build` <!-- NEXT_JS_LLM --> Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Will Binns-Smith <755844+wbinnssmith@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment