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

Fourteen files read process.env directly, and nothing validates it

Abierto
  • ¿Algo no está bien?
#338 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Stanley471 ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nodejs, postgresql, prometheus, redis, typescript
Área
backend

Línea de trabajo

Start with src/config.ts, which already reads process.env 34 times, then find the other direct reads in src/db.ts, src/app.ts, src/index.ts, src/api/admin.ts and src/bazaar/rateLimit.ts. Move parsing into one zod-validated module that fails at startup and names the bad variable, and check the result against .env.example with the drift guard, run through npm test (vitest). Done means process.env is read in exactly one module and a non-numeric numeric variable is rejected.

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

Descripción

area:config difficulty:intermediate help wanted points:150 Stellar Wave
Background

src/config.ts exists and is 333 lines, reading process.env 34 times. It does
no validation — no schema, no zod, despite zod already being a dependency used
for route validation. And 14 other files under src/ read process.env
directly, bypassing it entirely, among them src/db.ts, src/app.ts,
src/index.ts, src/api/admin.ts and src/bazaar/rateLimit.ts.

The failure mode is a misspelled or missing variable becoming undefined, then
a default, then a service that starts cleanly and behaves wrongly. A numeric
limit read as undefined silently becomes NaN in arithmetic. Nothing fails
until a price is wrong.

What to build
  • One validated config module as the single source: parse and validate the whole
    environment once at startup with zod, and fail to start on anything invalid.
  • Types derived from the schema, so a typo in a config key is a compile error.
  • Replace the 14 direct reads with imports from it.
  • Every variable documented in .env.example. The repo has a drift guard that
    checks this — run it.
  • Required-in-production variables must be required, not silently defaulted.
Acceptance criteria
  • process.env is read in exactly one module
  • Invalid or missing required configuration fails at startup with a message naming the variable
  • Config values are typed from the schema
  • .env.example documents every variable and the drift guard passes
  • A numeric variable that is not a number is rejected rather than becoming NaN

Drips Wave · Complexity: Intermediate · 150 points

Repo: Divinity-Labs/Lens. Node + TypeScript, Fastify, Prisma on Postgres,
Redis for queues, Prometheus via prom-client.

Run the tests: npm test. The tests are vitest, not jest. Running jest
against this repo reports "66 suites, 0 tests" and means nothing. A single file
is npx vitest run src/__tests__/yourfile.test.ts.

Load test (prices) is already failing on main and has been for some
time. It is not your PR that broke it. Every other check should be green.

This service prices real assets on Stellar mainnet. A number that is wrong
is worse than a number that is missing, because a caller cannot tell the
difference. Prefer failing loudly over returning a plausible value.

Never elide an address, a contract id or a key in code, a comment or a test
fixture. A previous batch wrote a shortened contract id in an issue text and
five contributors invented plausible-looking ids to fill the gap. Write the
whole thing or do not write it at all.

The house pattern for an outbound deadline already exists — see
src/alerts/delivery.ts, which passes signal: AbortSignal.timeout(10_000) to
fetch. Where an issue below asks for a timeout, copy that, do not invent a
second convention.

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

Lenguaje dominante
TypeScript
Estrellas
4
Forks
71
Merge medio
1 d 15 h
PR fusionados (30 d)
28

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 Divinity-Labs/Lens

Todos los issues de Divinity-Labs/Lens

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.