Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add an in-browser pack workshop with live diagnostics, verification and play

Aperta
  • Qualcosa non va?
#23 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript, web-dev
Ambito
developer-experience, frontend

Direzione di ricerca

Read the referenced ADR 0009 consequences and the import exploration in apps/web/src/screens/create.ts first, then review packages/engine/src/index.ts and packages/cli/src/commands/new.ts. The work spans an editor decision, worker diagnostics and verification, offline draft storage, export, playback, lazy loading, and an end-to-end test. Done means the listed acceptance criteria pass, including unchanged lexvm check output and no main chunk growth.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: web priority: medium type: feature

Context

Today an author needs the CLI, or must round-trip through an AI chat and the import screen, to fix a pack. A workshop in the player gives authors on tablets and laptops an offline edit, check and play loop. ADR 0009 says the UI decision should be revisited when a workshop is built. Builds on the import exploration in a Web Worker.

Scope

  • A lazily loaded workshop screen that edits multi-file packs (pack.yaml plus further files) stored on the device. Start from an imported pack, the demo pack or the same template as lexvm new.
  • Live diagnostics: debounced compile and analysis; tapping a diagnostic jumps to its file and line.
  • Verify: walkthrough replay, exploration and play-time estimate in the Web Worker, with dead-end paths.
  • Play the current draft from the start, or from any step of the walkthrough.
  • Export the files and a compiled .lexpack.json.
  • Editor approach decided in an ADR: a plain text area with line numbers, or a code editor component (a new runtime dependency), together with the question from ADR 0009 whether the UI still needs no framework.
  • Workshop code is not part of the main chunk.

Acceptance criteria

  • An ADR on the editor approach is accepted.
  • Changing a reference in the demo pack to an unknown id shows ref.unknown-object with file and line within one second.
  • Verify shows walkthrough, exploration and play-time results without blocking input.
  • Drafts survive a reload and work offline; exported files pass lexvm check unchanged.
  • An end-to-end test covers edit, diagnostics, verify and play.
  • The main chunk does not grow.

References

  • apps/web/src/screens/create.ts
  • packages/engine/src/index.ts
  • packages/cli/src/commands/new.ts
  • docs/adr/0009-vanilla-typescript-ui.md (Consequences)
  • docs/architecture.md (section 9)
Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
28m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nullthrone/lexvm

Tutte le issue di nullthrone/lexvm

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.