Add Vite build step to CI pipeline #27
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The CI workflow (
ci.yml) only runs PHP checks (Pint, PHPStan, PHPUnit) but does not build frontend assets. This means broken JS/TS imports (like thedashboardroute that broke the v0.2.0 image build) are not caught until the Docker image build step.Problem:
npm run buildis only run duringdocker build(Dockerfile line 51)release/*and PR tomain— neither catches frontend build failuresFix:
Add a Node.js setup +
npm ci+npm run buildstep toci.yml, running before PHP tests. This catches:Scope:
node_modulesviapackage-lock.jsonhashnpm run buildas a CI stepnpm run lint) as a separate stepThis ensures both pushes to
release/*and PRs tomainvalidate the full build.Closing as folded into the new M1 (Foundation) milestone. In the Symfony + standalone React/Vite rebuild, the SPA build is no longer an add-on to gate — it's structural: the production image has two build stages (composer + vite build) and CI must build/lint/test the frontend as a first-class artifact. This is covered by M1's "re-derive the full CI/build pipeline" scope rather than a standalone ticket.