System:
OS: macOS 14.3.1
CPU: (10) arm64 Apple M1 Pro
Memory: 112.91 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.18.1 - ~/Library/Caches/fnm_multishells/66181_1711122384805/bin/node
Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/66181_1711122384805/bin/yarn
npm: 9.2.0 - ~/Library/Caches/fnm_multishells/66181_1711122384805/bin/npm
pnpm: 7.26.2 - ~/Library/Caches/fnm_multishells/66181_1711122384805/bin/pnpm
Browsers:
Chrome: 123.0.6312.59
Edge: 122.0.2365.92
Safari: 17.3.1
npmPackages:
typescript: ^5.4.3 => 5.4.3
As described in the title, when using project references with disableSourceOfProjectReferenceRedirect
set to true
and declaration maps enabled, go to definition stops working. Works fine if disableSourceOfProjectReferenceRedirect
is set to false
.
It seems going to definition just brings you to the closing bracket of the outermost router.
https://github.com/relsunkaev/ts-declaration-map-repro
Try going to definition of a router from api client. See where that gets ya.
I have a suspicion that this is a typescript bug, but wanted to check with you guys first before submitting an issue there. Our repo has gotten quite large and disableSourceOfProjectReferenceRedirect
is the difference between waiting 5-10 seconds on every change and instant feedback in VSCode
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too