feat: enable React profiling build for dogfood (#23354)

mafredri · web-flow · commit e463adf6cb96 · 2026-03-24T18:46:11.000Z
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
@@ -1217,6 +1217,12 @@ jobs:
           EV_CERTIFICATE_PATH: /tmp/ev_cert.pem
           GCLOUD_ACCESS_TOKEN: ${{ steps.gcloud_auth.outputs.access_token }}
           JSIGN_PATH: /tmp/jsign-6.0.jar
+          # Enable React profiling build and discoverable source maps
+          # for the dogfood deployment (dev.coder.com). This also
+          # applies to release/* branch builds, but those still
+          # produce coder-preview images, not release images.
+          # Release images are built by release.yaml (no profiling).
+          CODER_REACT_PROFILING: "true"
 
       # Free up disk space before building Docker images. The preceding
       # Build step produces ~2 GB of binaries and packages, the Go build
diff --git a/site/vite.config.mts b/site/vite.config.mts
@@ -7,6 +7,14 @@ import type { PluginOption } from "vite";
 import checker from "vite-plugin-checker";
 import { defineConfig } from "vitest/config";
 
+// Enable the React profiling build and discoverable source maps for
+// internal deployments (e.g. dogfood). The profiling build swaps
+// react-dom/client for react-dom/profiling, which keeps production
+// optimizations but leaves the <Profiler> onRender callback and
+// React Performance Tracks instrumentation intact. The overhead is
+// ~13% on the react-dom chunk size.
+const isProfilingBuild = process.env.CODER_REACT_PROFILING === "true";
+
 const plugins: PluginOption[] = [
 	react({
 		babel: {
@@ -42,7 +50,7 @@ export default defineConfig({
 	build: {
 		outDir: path.resolve(__dirname, "./out"),
 		emptyOutDir: false, // We need to keep the /bin folder and GITKEEP files
-		sourcemap: "hidden",
+		sourcemap: isProfilingBuild ? true : "hidden",
 		rollupOptions: {
 			input: {
 				index: path.resolve(__dirname, "./index.html"),
@@ -209,6 +217,15 @@ export default defineConfig({
 	},
 	resolve: {
 		alias: {
+			// In profiling builds, swap the production react-dom client
+			// bundle for the profiling variant so that <Profiler>
+			// onRender receives actual timing data.
+			// Note: react-dom/profiling is a superset of react-dom/client
+			// (16 vs 3 exports). If a future React major changes this
+			// relationship, the alias may need updating.
+			...(isProfilingBuild
+				? { "react-dom/client": "react-dom/profiling" }
+				: {}),
 			App: path.resolve(__dirname, "./src/App"),
 			api: path.resolve(__dirname, "./src/api"),
 			components: path.resolve(__dirname, "./src/components"),
