The Vite production build step was running `npm run build` which includes `tsc -b` in its chain. The repo has ~100 pre-existing strict TS errors (TS6133 unused vars, TS1294 erasableSyntaxOnly, JSX intrinsic-element types for custom elements) gated by the separate `tsc` step above with continue-on-error. `build:docker` is the script the Dockerfile actually uses to ship prod — it runs generate:component-svgs + generate:sitemap + vite build + prerender-seo. It skips `tsc -b` for the same reason the workflow's `tsc` step is continue-on-error. Verified locally: 285 SEO pages prerendered, vite build green. |
||
|---|---|---|
| .. | ||
| actions-cache-cleanup.yml | ||
| backend-e2e-tests.yml | ||
| backend-unit-tests.yml | ||
| build-espidf-toolchain.yml | ||
| discord-issues.yml | ||
| discord-release-notify.yml | ||
| docker-publish.yml | ||
| frontend-tests.yml | ||
| library-compile.yml | ||
| test-circuit.yml | ||