Follow-up from #13 (PR #21). Pre-existing — not caused by that change.
tsconfig.build.json emits .js.map and .d.ts.map, and files ships dist, but not src. So every published source map has a sources entry pointing at ../src/*.ts, which is not in the tarball.
Consequences for consumers:
declarationMap go-to-definition lands on nothing — the feature the maps exist for does not work.- Debuggers and stack-trace tooling resolve the maps, fail to find the sources, and fall back silently.
Two clean options, either acceptable:
- Ship the sources — add
"src" to the files allowlist. Larger tarball, working go-to-definition and debugging.
- Drop the maps — turn off
sourceMap / declarationMap in tsconfig.build.json. Smallest tarball, no dangling references.
Shipping maps without sources is the one combination that is strictly worse than either.
Tasks
Relates to #7 (first publish).
Follow-up from #13 (PR #21). Pre-existing — not caused by that change.
tsconfig.build.jsonemits.js.mapand.d.ts.map, andfilesshipsdist, but notsrc. So every published source map has asourcesentry pointing at../src/*.ts, which is not in the tarball.Consequences for consumers:
declarationMapgo-to-definition lands on nothing — the feature the maps exist for does not work.Two clean options, either acceptable:
"src"to thefilesallowlist. Larger tarball, working go-to-definition and debugging.sourceMap/declarationMapintsconfig.build.json. Smallest tarball, no dangling references.Shipping maps without sources is the one combination that is strictly worse than either.
Tasks
pnpm pack) installed into a throwaway consumer, not just the config — confirm go-to-definition resolves (option 1) or that no.mapfiles ship (option 2).publint/attwalready run in CI viapnpm check:package; confirm whichever option you take stays green.Relates to #7 (first publish).