Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: comprobar prerequisitos de toolchain antes de app:dev

Open
  • Is something wrong?
#89 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, rust, tauri, typescript
Domain
build-system, developer-experience

Research direction

Start by reading package.json to see how app:dev and app:build are defined, then review the documented Tauri prerequisites in README.md, README.es.md, and CONTRIBUTING.md. Implement the proposed checks in scripts/preflight.mjs for Windows and wire them into both commands. Done means each missing prerequisite produces a nonzero exit with an actionable message and installation links.

Written by the indexing model from the issue text.

Description

Pre-flight checks
  • Busqué en las issues existentes (estado all) y no encontré duplicados.
  • Entiendo que esta propuesta requiere revisión de producto antes de implementarse.
Problem to solve

Un clon fresco en Windows sin toolchain de Rust hace fallar npm run app:dev con un error crudo del CLI de Tauri:

failed to run 'cargo metadata' command to get workspace directory:
failed to run command cargo metadata --no-deps --format-version 1: program not found

Los prerequisitos están documentados (README.md, README.es.md, CONTRIBUTING.md, todos con link a los prereqs de Tauri), pero nada los verifica antes de correr el comando. El error nunca menciona Rust ni el link de instalación, así que un contribuidor nuevo queda en un dead-end diagnosticando un problema de entorno solo.

Proposed solution

Un preflight liviano y sin dependencias (scripts/preflight.mjs) enganchado a app:dev/app:build que verifique en Windows:

  • Node >= 22
  • cargo y rustc resolvibles en PATH (toolchain stable-msvc)
  • MSVC linker / VS Build Tools presentes
  • WebView2 runtime disponible

Si falta algo: exit non-zero con un mensaje accionable por pieza, con los links de instalación (https://v2.tauri.app/start/prerequisites/ y https://rustup.rs).

Affected area

Build or tooling

Scope and non-goals
  • Scope: solo detectar y reportar; envolver app:dev y app:build.
  • Non-goals: auto-instalar Rust/VS Build Tools, modificar el PATH del usuario, cubrir CI (ya instala su propia toolchain) ni detección macOS/Linux (el target actual es Windows).
Alternatives considered
  • Solo docs: ya está documentado en 3 lugares; quien se los salta igual muere en el mismo error críptico.
  • Detectar tras el fallo del CLI de Tauri: string-matching frágil contra salida upstream, en vez de verificar los prerequisitos directo.
  • engines en package.json: npm solo advierte por defecto y no puede expresar cargo/MSVC/WebView2.
Dominant language
TypeScript
Stars
10
Forks
2
Avg merge
21m
Merged PRs (30d)
52

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from egdev6/quorb

All issues in egdev6/quorb

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.