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

Incorrect sourcemap sources paths when outDir differs from source directory

Aperta
  • Qualcosa non va?
#1,966 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
build-system

Direzione di ricerca

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.

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

Descrizione

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"]      ✅
Lingua principale
JavaScript
Stelle
3.8k
Fork
636
Nessuna PR unita negli ultimi 30g

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

Tutte le issue di rollup/plugins

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.