Incorrect sourcemap sources paths when outDir differs from source directory

Abierto
#1,966 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
build-system

Línea de trabajo

Start in packages/typescript/src/outputFile.ts, specifically findTypescriptOutput, and reproduce the issue with the linked project using npm install, npm run build, and jq on dist/project-1/index.js.map. Trace how the emitted sourcemap sources are returned and ensure the final sources resolve to my-project-1/src/test.ts as ../../my-project-1/src/test.ts.

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

Descripción

Expected Behavior

When the TypeScript source files live in a different directory tree than the outDir, the final bundled sourcemap should contain correct relative sources paths that resolve back to the actual .ts files.

For the reproduction project with source at my-project-1/src/test.ts and output at dist/project-1/, the sourcemap should contain:

"sources": ["../../my-project-1/src/test.ts"]

Resolving from the map file's directory: resolve("dist/project-1", "../../my-project-1/src/test.ts")my-project-1/src/test.ts

Actual Behavior

The sourcemap contains an incorrect path with one extra ../ level:

"sources": ["../../../my-project-1/src/test.ts"]

Resolving from the map file's directory: resolve("dist/project-1", "../../../my-project-1/src/test.ts") → goes above the project root ❌

This breaks source mapping in browsers, debuggers, and any other sourcemap consumer.

Additional Information
Root cause

TypeScript emits sourcemaps with sources paths relative to the output map file location (inside outDir). For example, when compiling my-project-1/src/test.ts with outDir: "../dist/project-1", TypeScript would write dist/project-1/src/test.js.map containing:

{ "sources": ["../../../my-project-1/src/test.ts"], "sourceRoot": "." }

This is correct when resolved from the map file's directory (dist/project-1/src/):

path.resolve("dist/project-1/src", ".", "../../../my-project-1/src/test.ts")
→ "my-project-1/src/test.ts" ✅

However, @rollup/plugin-typescript returns this sourcemap verbatim from the load hook. Rollup's getCollapsedSourcemap then resolves these source paths relative to path.dirname(id) — the original source file's directory (my-project-1/src/), not the output map file's directory:

path.resolve("my-project-1/src", ".", "../../../my-project-1/src/test.ts")
→ "../my-project-1/src/test.ts"  (one level above project root) ❌

The mismatch occurs in findTypescriptOutput (packages/typescript/src/outputFile.ts), which returns the TypeScript-emitted sourcemap without rebasing the sources paths from the output directory to the source file directory.

Steps to reproduce
git clone https://github.com/skrtheboss/rollup-repro-5sqw8ygm
cd rollup-repro-5sqw8ygm
npm install
npm run build
cat dist/project-1/index.js.map | jq .sources
# Actual:   ["../../../my-project-1/src/test.ts"]  ❌
# Expected: ["../../my-project-1/src/test.ts"]      ✅
Lenguaje dominante
JavaScript
Estrellas
3.8k
Forks
635
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

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 rollup/plugins

Todos los issues de rollup/plugins

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.