# Frontend checks in CI

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Frontend area: Second app, UI, browser tests.

Page: https://gradus.kazet.blog/tree/cloud-application/step/frontend-ci

Lint, type check, unit tests, a size budget and a production build of the frontend on every push, with development-only code kept out of what ships.

Usually comes after: [The first journey in the browser](https://gradus.kazet.blog/tree/cloud-application/step/journey-ui).

## Prompt for your AI assistant

```
Add the frontend's checks to CI: lint, type check, unit tests and a production build on every push and pull request, as a job in the existing workflow for a workspace or as the frontend repository's own workflow. Cache dependencies, fail on warnings in the build and publish the built files as a workflow artifact. Set a size budget for the JavaScript the first page loads and fail when it is exceeded. Keep development-only code such as fixtures, debug pages and unreleased features out of the production build behind a build-time switch, and add a check that searches the built files for a marker from each.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt