From c534e4f5d864fa728c6b81dde43d9d896e45416c Mon Sep 17 00:00:00 2001 From: Roland Date: Sun, 2 Aug 2026 13:07:08 -0600 Subject: [PATCH] dev: stop the app container linting on every rebuild react-scripts lints in-process on every incremental rebuild. Each save pays for it, and the result is buried under a few hundred warnings the repo has carried for years -- `no-useless-computed-key` on the wire-gauge tables, `react-hooks/exhaustive-deps` across most of Common.js. Finding "Compiled successfully" in that takes a scroll. This container only serves; it never builds. Linting still happens where it is acted on: `npm run build` and CI both run it, and both fail on a real error. NOT a memory fix, though that is why I reached for it -- the dev server was OOM-killed three times in an afternoon and I claimed this would be the biggest saving. It is not. Measured both ways with the same procedure (recreate, load a page, wait for the typecheck, read `docker stats`) the container settles at 3.5GB with linting and 3.0GB then 3.7GB without it. The spread between two runs of the SAME configuration is wider than the spread between configurations, so the effect is below what this can measure. Raising Docker Desktop's VM limit from 8GB to 16GB is what actually stopped the kills. Kept anyway, on the time and the noise, which are not in doubt. Co-Authored-By: Claude Opus 5 (1M context) --- docker-compose.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index d8aa1d20..b21d37bd 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -90,6 +90,17 @@ services: environment: # Force React to use Caddy port to connect to it's websocket. - WDS_SOCKET_PORT=0 + # react-scripts lints in-process on every incremental rebuild, which costs time on each + # save and buries the compile result under a few hundred warnings the repo has carried + # for years. This container only serves; linting still happens where it is acted on -- + # `npm run build` and CI both run it, and both fail on a real error. + # + # NOT a memory fix, though it was tried as one after the dev server was OOM-killed three + # times in an afternoon. Measured either way, the container settles anywhere between + # 3.0GB and 3.7GB and the spread between two runs of the SAME configuration is wider + # than the spread between configurations. Raising Docker Desktop's VM limit is what + # actually stopped the kills. + - DISABLE_ESLINT_PLUGIN=true web: # Caddy reverse proxy - handles HTTPS for all services. depends_on: