code-check-client-bundle

Detect server leakage in a client bundle by applying server-vs-client boundary heuristics to flag Node-only modules and DB libraries imported into browser code. Scoped diff-based detection prevents accidental server dependencies from breaking client runtime execution.

Environment variable safety works by identifying `process.env.*` usage in client files to highlight non-public secret exposure or undefined runtime values. This prevents accidentally bundling sensitive backend configuration into the browser payload.

Check for client bundle weight regressions by running scoped diff-based detection after dependency changes to warn when heavy libraries are statically imported. This catches newly added packages inflating initial first-load JavaScript without scanning the whole repository.

Yes, this client bundle check works with TanStack Start, Next.js, and Vite projects. It applies after client code or dependency changes, using scoped diff-based detection rather than whole-repo scans to find server leakage and heavy dependencies.

The best way to flag unoptimized media assets in a diff is through targeted asset risk flagging, which checks added or changed images and video for oversized files. This catches unoptimized sizes that hurt performance budgets before deployment.