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

Turbo: lsp/markdownit/editor builds write outside declared outputs, so cache hits don't restore them

Abierto
  • ¿Algo no está bien?
#1,144 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
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript, vite
Área
build-system, tooling

Línea de trabajo

Start with turbo.json and the build entry points in apps/lsp/build.ts, apps/vscode-markdownit/vite.config.ts, and apps/vscode-editor/vite.config.ts. Review deps-upgrade-turbo.md and the vscode:prepublish command to understand the current Turbo constraints. Done means a clean checkout and cached turbo run build restore the LSP, markdown renderer, and editor outputs without relying on --force.

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

Descripción

Problem

turbo.json declares the build outputs as ["dist/**", "out/**"], relative to each workspace. Several builds write into another workspace instead:

Workspace Writes to
apps/lsp (build.ts) apps/vscode/out/lsp/ (lsp.js, wasm, resources)
apps/vscode-markdownit (vite.config.ts) apps/vscode/out/markdownit/
apps/vscode-editor (vite.config.ts) apps/vscode/assets/www/editor/

Turbo only caches and restores declared outputs inside the task's own package, so on a cache hit for these tasks the files in apps/vscode are not restored. After a clean checkout or rm -rf out, a cached turbo run build can report success and leave apps/vscode without the LSP, the notebook renderer or the visual editor bundle.

This is presumably why vscode:prepublish uses turbo run build --force --filter quarto... (added in 5fd360d9, "force rebuild for vsce package"). --force disables the cache for the whole graph, and local dev builds can still produce this failure.

Fix options

  1. Preferred: have each workspace build into its own dist/, and have apps/vscode's build copy them into out/ and assets/. Then turbo's outputs are accurate, and --force can be dropped.
  2. Or declare per-package outputs with a path relative to the package (e.g. "outputs": ["../vscode/out/lsp/**"] in an apps/lsp/turbo.json). Turbo 1.x has limited support for outputs outside the package, so check this against Turbo 2, which the upgrade plan moves to anyway (deps-upgrade-turbo.md).
  3. Or mark these tasks cache: false.

Note that apps/vscode/assets/www/editor isn't in any outputs at all, so that one isn't cached even conceptually.

Found during the dependency-upgrade research.

Lenguaje dominante
TypeScript
Estrellas
652
Forks
64
Merge medio
8 h 45 min
PR fusionados (30 d)
36

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 quarto-dev/quarto

Todos los issues de quarto-dev/quarto

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.