Run Lighthouse in CI for accessibility and performance

Abierto
#136 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, typescript, vite

Línea de trabajo

Start by reading the existing workflows in .github/workflows/ and the build and preview scripts in apps/web/package.json, then docs/PERFORMANCE.md for current targets. Add a workflow that builds the web app, serves it with vite preview, and runs Lighthouse CI on the five listed pages with a path filter for apps/web. Done means failures name the page and audit, the report is saved as an artifact, and the run finishes in under 10 minutes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

accessibility ci help wanted

Difficulty: Intermediate · Estimated size: 1 day

Context

Accessibility and speed matter for a community platform, but they are only checked by hand.

Problem or goal

Run Lighthouse against the built site for the public pages and report the scores on each pull request.

Suggested approach

  • Use Lighthouse CI against vite preview for /, /explore, /login, /register, /privacy.
  • Set minimum scores (for example accessibility 95, best practices 95, performance 80 on a throttled mobile profile). Start with warnings, then make them required once stable.
  • Save the report as a workflow artifact.

Where to look

  • .github/workflows/
  • apps/web/package.json
  • docs/PERFORMANCE.md

Acceptance criteria

  • The workflow runs on pull requests that change apps/web.
  • Failures name the page and the failing audit.
  • Runs finish in under 10 minutes.

How to work on it

  1. Comment here to claim it, so two people do not do the same work.
  2. Fork the repo and branch from main (feat/short-name or fix/short-name). Setup steps are in docs/DEVELOPMENT.md.
  3. Keep the change focused and add tests for backend logic.
  4. Run npm run typecheck, npm test and npm run lint and npm run format before opening the pull request.
  5. Use a Conventional Commits title (for example feat(web): add bookmarks). More in CONTRIBUTING.md.

Stuck? Ask in this issue. Questions are welcome.


Generated by Claude Code

Lenguaje dominante
TypeScript
Estrellas
6
Forks
6
Merge medio
1 h 59 min
PR fusionados (30 d)
59

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Haseeb-MernStack/commune

Todos los issues de Haseeb-MernStack/commune

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.