Error in 'getExportEqualsLocalSymbol' during 'documentHighlights' #39584
Comments
typescript-bot
added
Bug
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
Probably fixed, no repro since August https://github.com/microsoft/tsserverfuzzer/issues/263 |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
There's a lot of "unknown (suppressed.js)" in the bot comments so I'll post a full stacktrace here since the issue keeps happening to me: I know this isn't VSCode, it's VSCodium, but the line/columns for tsserver.js are exactly the same so I think it's the same issue. |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
@heyheyhello we're having trouble reproducing this; do you have a repro project you could share? |
|
Unfortunately I don't, it's all private code. I tried to reproduce this for a while last night by readjusting my tsconfig to match what I had back in May. I tried both TS 4.3.5 and TS 4.2.1 but never had the same error come up; I get a new, different, error this time for the same actions (logs attached below). VSCode has updated a few times which might be why the error is different... Very shortly after posting #39584 (comment) I stopped trying the tsconfig that caused the error. I thought I was just overloading the TS server, I don't blame it. Here's what I was trying to do: My team develops in a monorepo and we publish internal packages for other teams to use. Many teams at our company do this. When I started working here I noticed every team publishes the code as minified+polyfilled webpack bundles even though they develop the source code in TypeScript... This meant ctrl+clicking an import would open up the meaningless minified code from node_modules. Teammates said I should just read source code in our GitLab... Instead, I tried doing a git checkout of few teams' repos and used a jsconfig.json to redirect imports to the source code. The idea was that I'd get readable code when I ctrl+click imports and I'd get properly typed imports since the other teams develop in TS! (We had yet to start developing in TS at the time, hence the jsconfig.json; today we have tsconfig). Maybe you'd agree it's a bad idea: each repo is huge and has many packages and may have multiple tsconfigs. I'd hover on an import statement and it'd crash. Here's a screenshot I found from back in May of the jsconfig. I'm using
Last night I tired it again and was very surprised to see it work! It's a bit slow, but it works! I had 20 or so If you're curious, the new error is about not being able to find the file path (even though it's the file I'm staring at in my editor). Similar to the error in May, both only happen when I hover on an import such as vscode-ts-error-4.1.2.log TL;DR This error doesn't happen to me anymore and I was probably asking for it by misusing TypeScript at the time. I try to be nicer to the TS server these days. Thanks! |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
|
This issue reproduced in the following context: |
This issue comes from crash dumps in telemetry. We've tried to de-duplicate issues on a best-effort basis, comparing the sequence of methods called and the command requested while ignoring line numbers.
TypeScript version prefix: 3.9.6
VSCode version: 1.47.0
Command requested: documentHighlights
Hitting sessions: 5942
Five line hash: 484743baaede160b2fba00a271553832
Stack:
The text was updated successfully, but these errors were encountered: