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

pnpm check-types only checks 2 of 10 packages, so CI's type gate is mostly empty

Abierto
  • ¿Algo no está bien?
#189 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Blazehue ya está trabajando en esto.

Desde el 26/10/2026.

  • #222 de @Blazehue — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript, vite
Área
build-system, ci-cd

Línea de trabajo

Start by reading .github/workflows/ci.yml, the root package scripts and turbo.json, then compare the package.json files for the listed apps with genai and @repo/ui. Check each package’s TypeScript project configuration, especially the frontend build setup, before adding the missing checks. Run pnpm run check-types and verify a deliberate type error in http-server or frontend makes it fail.

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

Descripción

Backend first issue bug good first issue help wanted nsoc26

CI presents this as the type-safety gate:

# .github/workflows/ci.yml
      - name: Type-check
        run: pnpm run check-types

But most packages do not define the script, so turbo finds almost nothing to run:

• Packages in scope: @repo/db, @repo/eslint-config, @repo/typescript-config,
                     @repo/ui, admin, admin-server, frontend, genai,
                     http-server, ws-server
• Running check-types in 10 packages
 Tasks:    2 successful, 2 total

Only genai and @repo/ui have it. frontend, http-server, ws-server, admin, admin-server and @repo/db are all skipped, and turbo exits 0 regardless.

Why it matters

A contributor can break every type in http-server or the whole frontend and CI stays green. The step looks like protection and provides almost none — which is worse than having no step, because reviewers trust it.

What a fix looks like

Add the script to each package that is missing it:

"check-types": "tsc --noEmit"

The frontend builds with tsc -b && vite build, so it may want tsc -b --noEmit or its existing project reference instead — worth checking what that package actually needs rather than pasting the same line everywhere.

You will not inherit a pile of errors. I checked both servers before filing:

apps/http-server  tsc --noEmit -> 0 errors
apps/ws-server    tsc --noEmit -> 0 errors

So this is additive. If admin or admin-server turn out to have existing errors, say so in the PR rather than fixing them in the same change — those can be their own issue.

Definition of done
  • pnpm run check-types reports more than 2 total (6+ depending on what you include)
  • A deliberate type error in http-server or frontend makes the command fail
  • CI goes red for that deliberate error, then green once reverted

Good first issue: a few lines of JSON, and it turns a decorative CI step into a real one. Verify it works by breaking a type on purpose before you open the PR.

Lenguaje dominante
TypeScript
Estrellas
21
Forks
7
Merge medio
5 h 19 min
PR fusionados (30 d)
29

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 TheCodeHeist-Coder/Rexial

Todos los issues de TheCodeHeist-Coder/Rexial

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.