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

Add Void to Framework Tracker

Abierto
#683 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, react, typescript, vite

Línea de trabajo

Start by reading .github/frameworks.json and the existing starter packages to understand their registration and measurement conventions, then review Void’s quickstart and Node target documentation. The proposal calls for a starter-void package, framework registration, and methodology documentation; a starter-only entry should record dependency footprint, install time, and build time, with the UI adapter choice confirmed.

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

Descripción

I’d like to propose adding Void to Framework Tracker.

Void is an open-source full-stack framework by VoidZero. It's powered by Vite and provides file-based API routes and server-rendered pages with React, Vue, Svelte, or Solid.

I suggest starting with a starter-only entry covering dependency footprint, install time, and build time. The contribution would include:

  • A starter-void package generated through the official setup workflow, with an exact framework version, an independent lockfile, and a first-party dependency manifest.
  • Registration in .github/frameworks.json with focusedFramework: false.
  • Methodology documentation covering the selected UI adapter, starter options, and build configuration.

Runtime benchmarks could follow using either:

  • Node: Use Void’s Node target with the existing harness.
  • Workers: Run locally in workerd for browser and HTTP load tests; direct handler throughput needs more integration.

Would you be open to this addition? If so, is there a preferred UI adapter for the initial starter. Otherwise I'd default to React since it's the most popular right now.

I’d be happy to prepare the PR.

Lenguaje dominante
TypeScript
Estrellas
42
Forks
16
Merge medio
13 h 59 min
PR fusionados (30 d)
148

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 e18e/framework-tracker

Todos los issues de e18e/framework-tracker

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.