-
Notifications
You must be signed in to change notification settings - Fork 12.8k
IntelliSense typing info in 2.9.0-dev.20180407 release doesn't work #23255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So I tried going back through previous typescript versions, and have found that the 2.4.2 release does not have either the problem outlined above, or the issue I posted about in #23234 So until this issue is resolved, I'll just stick to that version. |
Can you please provide tsserver and typing installer logs. Also your package.json, Also let us know if you have explicitly installed any modules and typings. Thanks. |
I've started having intellisense issues in February's 1.21 update. Ever since it's been failing after a while, but 1.22 completely broke it. It just doesn't work, and reverting back to typescript 2.81 or 2.4.2 doesn't work either. What worked for me was actually installing January's 1.20.1 vscode. It comes with typescript 2.8.1, and it works fine. I didn't even try any other typescript versions because I was afraid it would break things again. So maybe it's not only on typescript, since 2.8.1 works fine with vscode 1.20.1: intellisense is smooth as it always been. I have absolutely no use for typescript, I don't use it at all, so having a version that just makes vscode intellisense work is fine by me, whatever version that is. |
relevant package.json bits:
@sheetalkamat I'm not sure what you mean by typing installer logs; can you be more specific? Either way, I've just uploaded both of the files that showed up in the tsserver log folder: As for explicitly setting typings, if I'm understanding you correctly, no I haven't. I did get it to work though by manually installing them from npm. Curiously a lot of typings are missing from the 2.9 installation: |
Oops, sorry for the accidental close. Just to add, note I'm using 2.9.0-dev.20180410 now from typescript@next, but the issue is still there. I can put together a repo again if need be, but the repo from the other issue I posted would suffice for testing it. |
Hi @sheetalkamat, is there any update on this issue? |
Seems like typing installer is failing and resulting in no npm packages for the types and hence no intellisense. From the shared ti log it looks like package for @types/chokidar doesnt have 2.9 version which results in failure to install any package. @Andy-MS is looking into why there is no 2.9 version on that package. |
Sounds good. Let me know if I can provide a repo if it helps tracking the issue down. |
@RonanQuigley Repro code would be great help to ensure that this is fixed correctly and also investigate if there are any other perf tweaks possible. |
Sorry for the delay in getting back. So I now can't get the issue to consistently repro. Have been fiddling with it for about 30 mins and has happened three times in that time, but all of the steps that caused it were completely unrelated and random. The only constant is it happens after a period of time about 5 minutes. I've tried to reduce my repo from the prev issue I posted down to a minimal size, but I've chosen to keep it as is (bar updated to typescript 2.9) as the issue could be tied to project size. I did reduce it to a couple of files but it never happened in that case. I can appreciate this won't be ideal for tracking down the issue, so if you're unable to repro with this I'll understand. https://github.com/RonanQuigley/vscode-intellisense-bug As an aside, why is it that the code completion does not work in the following scenario: Here I've declared a variable at the top, set it to a value inside a function, then attempt to use auto completion further down the file but it comes back blank? |
@RonanQuigley I believe that situation is basically: let x;
function f() {
x = 0;
x.toExponential(); // Get completions for number
}
function g() {
x. // Get no completions
} The things is that immediately after the |
@Andy-MS Ah yeah that makes sense. Thanks for the clarification. @mhegazy Was the bug label removed for that aside question or the main issue I posted about, as nobody has said either way whether or not this can be replicated with the repo I posted? If you need something more definitive then I'm out of ideas unfortunately. Until then I'll just stick with an earlier version of typescript. |
Okay so initially I thought I was being an idiot, as I realised I didn't actually have react or react-dom in the dependencies, which is what I was trying to repro this issue with. 😆 Weirdly there was code completion showing up without either being installed; I guess it was looking inside another typescript version folder? I did also have another vscode project open in the background.. Either way, even after installing any missing modules it still happens. And with other already installed modules. This time I did get it to happen twice: Hope this helps. |
@RonanQuigley Thank you for the logs. I was able to use the logs to investigate this. Will keep you posted when i have fix available. |
…ferred project root, is opened right after closing the root file Fixes the crash reported in #23255 (comment)
…ferred project root, is opened right after closing the root file Fixes the crash reported in #23255 (comment)
…ferred project root, is opened right after closing the root file Fixes the crash reported in #23255 (comment)
@RonanQuigley can you please try out |
Tried it, still the same problem: And this was the result after a while of fiddling |
@RonanQuigley Looking at the log there wasnt a single completion that took more than 350 ms. Can you please check if the logs are of session in which the issue reproed. |
I took a second look at the logs and i think the issue you are seeing now is duplicate of #19458 where i think it might be same reason as geterr triggered before completion resulting in the wait you see in editor but not in the log. This is because tsserver is working on getErr request and since its not cancelled it cannot get to completions before that work is complete. Snippet from the log which makes me guess that #19458 is same issue.
|
Hey, sorry for the delay in responding. I had to put this down due to other work. I looked through the other issue and it says it is to do with the sass.js module? I'm not using that module in the project. Do you want me to reproduce the logs again? |
@RonanQuigley Fix for #19458 is not yet working from vscode side. I will let you know once its available. Even though issue #19458 talks about sass.js it has nothing to do with the module dependency itself but about how errors and completions request interact with each other. |
Not sure if it's related to this issue, but thought it might be worth mentioning that the latest releases of typescript (currently I've tried 2.9.0-dev.20180519) seems to have helped quite a bit. I still get an occasional crash during the day, but it's not as frequent. |
@RonanQuigley Can you please share the server and ti log when you see crash. The previously encountered crash was fixed in #23636 |
Closing this since there is no more info since May. If you have more info and able to repro this with latest typescript and vscode drop please provide that. |
TypeScript Version: 2.9.0-dev.20180407
Search Terms: intellisense, missing types
Perhaps I'm missing something here, as I don't use typescript and have always just used the version that vscode ships with for intellisense, but after updating to the latest for a fix of a prev issue I posted about (see bottom) I now have the following issue.
See the following gifs for an explanation:
Expected behavior:
This is what happens in version 2.8.1. It also successfully recognises the type definitions file.
Actual behavior:
This is currently what happens in the 2.9.0-dev version. The type definitions file is not found.
Furthermore it happens with any module e.g this is the react one. Note that it works initially then just fails afterwards:
Workaround:
I can get it to work again by manually installing each of the types i.e
@types/chai
etc. However that's not ideal so I've reverted back to 2.8.1 for the time being.Related Issues:
I brought up an issue with intellisense crashing in 2.8.1, but am unsure if this is a side effect from that or just another issue entirely. So whilst the path issues are fixed in 2.9, the outlined issue above now shows up.
#23234
I can provide the typescript log in private if need be.
The text was updated successfully, but these errors were encountered: