Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Set and enforce performance budgets for v1.0

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/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 with docs/architecture.md and the referenced Vite, precache, performance test, and CI workflow files to understand the existing bundle budget and measurement setup. Define repeatable measurements for startup, offline page and precache size, and pack checking time and memory, then document budgets and how pull requests can raise them. Add CI checks and demonstrate a failing budget with a test change; done means the documented budgets are met at v1.0.

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

Descripción

area: infra area: web priority: medium type: chore

Context

v1.0 promises a dependable player on low-end phones and a verifier that stays usable as packs grow. The v0.2 bundle-size work (#34) adds a CI budget for the main chunk. Other costs are not measured: start-up time on a slow phone, the size of lexvm-offline.html and of the precache as packs are added, and the time and memory of npm run check:packs (the explorer uses about 1.8 KB per state). Baseline at the v0.1 pull request (Vite report): main chunk 270 KB (85 KB gzip), Create screen 148 KB (54 KB gzip), YAML compiler 102 KB (32 KB gzip), CSS 26 KB (6 KB gzip), lexvm-offline.html 660 KB (209 KB gzip); the service worker precaches 16 files; the noir pack's .lexpack.json is 100 KB.

Scope

  • Measure and record budgets in docs/architecture.md: start-up time to an interactive library and game screen on a throttled mobile profile, lexvm-offline.html size, precache size, npm run check:packs time and peak memory.
  • CI checks for each budget, including the main chunk budget from v0.2, with a documented way to raise a budget in a pull request.

Acceptance criteria

  • Budgets and the measuring method are documented.
  • CI fails when a budget is exceeded (shown with a test change).
  • All budgets are met at the v1.0 release.

References

  • apps/web/vite.config.ts
  • apps/web/build/precache.ts
  • packages/engine/test/explore-perf.test.ts
  • .github/workflows/ci.yml
  • docs/architecture.md
Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
28 min
PR fusionados (30 d)
2

Preparar el entorno

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 nullthrone/lexvm

Todos los issues de nullthrone/lexvm

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.