Repository navigation
Clarity about the what path references are relative to #50529
Description
Suggestion
🔍 Search Terms
references path relative
✅ Viability Checklist
My suggestion meets these guidelines:
- [ x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x ] This wouldn't change the runtime behavior of existing JavaScript code
- [ x] This could be implemented without emitting different JS based on the types of the expressions
- [x ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x ] This feature would agree with the rest of TypeScript's Design Goals.
⭐ Suggestion
Both https://www.typescriptlang.org/tsconfig#references and https://www.typescriptlang.org/docs/handbook/project-references.html aren't specific about what the string in path is relative to (the current tsconfig, the current working directory, rootDir, etc)
💻 Use Cases
I'm writing some build scripts around invocations of tsc with a lot of linking, aliasing, etc and I don't want to put absolute paths in the generated tsconfig files
Activity
fatcerberus commentedon Aug 29, 2022
IIRC all paths in a tsconfig are relative to the tsconfig.
kwasimensah commentedon Aug 29, 2022
I figured as much. But given:
https://www.typescriptlang.org/tsconfig#baseUrl and https://www.typescriptlang.org/tsconfig#paths
https://www.typescriptlang.org/tsconfig#rootDirs
https://www.typescriptlang.org/tsconfig#preserveSymlinks
I've run into issues before where those complicated the paths used in look up by tsc
But I also see https://www.typescriptlang.org/tsconfig#files which I guess I took for granted my assumption that it's always relative to the tsconfig.json
kwasimensah commentedon Aug 30, 2022
So I realized, the feature request hiding in this question is if there could be a way to have a fixed root for tsconfig.json resolution.
Given root with:
a/tsconfig.json
b/tsconfig.json
c/tsconfig.json
if there was way to have the references be their root relative paths instead of having to calculate paths relative to each other