No IntelliSense for TS/JS files

[otbe]

Hi *,

I try to replace webstorm with vscode as my main development editor/IDE, but as of now its not possible for me. Im not sure if this is a bug or misconfiguration of my system but IntelliSense, "Go to definition" and other useful stuff don't work for JavaScript or TypeScript files. On the other hand "context-aware" JSONs like tsconfig.json, package.json do work like expected.

This is my test repo: https://github.com/otbe/vscode-intellisense-test

And this happens on my (and only on my) machine:

I have made no changes to the default settings of vscode.

Grateful for every hint :/
Thanks.

Versions:

• VSCode Version: 0.10.14-insider | 0.10.11
• OS Version: OS X 10.11.3

[sgal]

Try to add files section in your tsconfig.json, like in this example
{ compilerOptions: {...}, files: ['./src/index.ts'] }

Not sure that will help, but that's the first thing that I would do.

[otbe]

Tried already to add files or exclude to my tsconfig.json, but this did not work for me. The test repo works as expected on my colleagues mac.

[djadu]

I'm having a similar problem, but I do get a warning message:

The Typescript language service died unexpectedly 5 times in the last 5 Minutes. Please consider to open a bug report.

[egamma]

I get Intellisense

And Peek Definition works as well

In your code you write let s = Person(), this should be flagged as an error

What version are you using (bit this has already worked in ancient versions). What I see in the screen shot is that the tsconfig.json isn't saved. Can you try to save and to execute the command Reload TypeScript project.

[otbe]

Hi @egamma

your screenshots show how it works on my colleagues mac. Im using the latest stable version and insiders (0.10.15-insider | 0.10.11). tsconfig.json was not saved only during screen recording :). A fresh clone of this repo did not work either.

Is it possible to activate verbose logging in vscode/tsc? Maybe vscode isn't communicating with the TS compiler API properly!?

EDIT:
On a windows VM on my mac it works as expected :)

[egamma]

The fact that you do not get squiggles indicates that the tsserver has crashed and isn't running, assigning to @dbaeumer.

[otbe]

But this misbehavior does not apply only to typescript.

Same example works fine in my windows vm or on other Macs

Edit: while browsing through a large JS project I get some logs like the following:

Dont know if this is related to my problem :)

[dbaeumer]

@otbe when the tsserver crashes we show a Message Box in the UI that informs you about this. Did you saw such a message box.

The error shown in the last comment is indeed related to editing JS files.
@jrieken: can you please look at this and may be create a separate issue.

[dbaeumer]

I tried to reproduce this on the insider 0.10.15 without any luck. And the project is more than trivial. So I doubt that this is a tsserver issue at all. @otbe can you think of any difference between the Macs with the different behaviour. Are you using nvm ?

[otbe]

@dbaeumer
Saw no such message box ever, but typescript has never worked for me in vscode. :)

But how I said, this problem is not only related to typescript. Simple JS files (see screenshot) did not work either.

Both macs using nvm (node 4 & 5).

Whats unique to my mac:

• brew is installed
• docker & docker related tools are installed

What I tried so far:

• installed typescript globally
• different node versions
• different vscode versions (insiders and stable)
• different user accounts (also newly created ones)

Did I miss something @donaldpipowitch?

Is there anything I can do to provide more information? Start vscode in another mode or something like this.

[donaldpipowitch]

I also use brew and nvm (but no docker tools). @otbe and I share a lot of projects and tools. We can't spot the difference in our setup. vscode works great for me.

[jrieken]

@dbaeumer The error message is triggered by the status info call but it hint towards us not yet have done a single openFile request. That's the reason why the call fails. Now I wonder why that it...

@otbe At the bottom of the editor it says JavaScript, TypeScript respectively?

[otbe]

@jrieken
Yes it recognizes JS/TS properly.

[jrieken]

Anything special about the file paths? Like ümlauts, network-share, sym links etc?

[dbaeumer]

@otbe Just for clarification: the tsserver powers both TS and JS. That is why both don't work in your setup.

[dbaeumer]

@otbe can you please try the following:

• set the global environment variable TSS_TRACE to 1 (in a shell)
• start VSCode from that shell
• in VSCode open the Developer Tools by pressing F1 and typing developer tools. Select Developer: Toggle Developer Tools
• open a TS file

You should see something like this in the console:

[dbaeumer]

@jrieken can you help with the env and starting from a shell on the Mac please.

[jrieken]

On the mac that would be export TSS_TRACE=1 && code

[otbe]

My output looks different (yeeah)

[jrieken]

Can you check your tsconfig.json-file for errors or warning and comments? Maybe tsserver fails to process that and therefore responds with No Project errors

[donaldpipowitch]

@otbe and I use the same repositories without any changes. It can't be really a project-specific reason. It must be his global setup somehow :(

[otbe]

@jrieken
@donaldpipowitch and @egamma used the same tsconfig.json without problems.

Is it possible to "debug" tsserver.js? Tried to place some console.logs inside getProjectForFile() but it crashes with unexpected end of input ...

EDIT:
same with 1.0.0

[otbe]

Maybe this is related to my problem. I use a case-sensitive filesystem on my mac.

[jrieken]

yeah, that might be something... How do you start vscode? just clicking the icon or via the code-command shell from terminal and iff so do you pass on the file to open? In that case we might infer the wrong casing, meaning file path.

Another case would be special characters in path names, we know that on mac characters sometime differ in how they are encoded. Anything non-ascii in your paths?

[otbe]

I just click the icon and open my project folder via File -> Open.
Project path is: /Users/boo/vscode-intellisense-test, tried also /tmp/vscode-intellisense-test

[dbaeumer]

@otbe: from the error message however it is clear that the file we are opening in the tsserver doesn't match the file name when asking for code complete. That is why the server response with no project info.

You can debug the tsserver by setting the env variable TSS_DEBUG to a port number. For example TSS_DEBUG=5859. Then you can attached a debugger like node inspector to the running server. I will think about what could cause this on Mac. I also will test you workspace on Linux which is case sensitive as well.

[otbe]

fileName and path differ and defaultProject is undefined...

This may be the root cause:

And this is a bit optimistic in my opinion :)

const useCaseSensitiveFileNames = platform !== "win32" && platform !== "win64" && platform !== "darwin";

[jrieken]

They should really not do that

[otbe]

If I change useCaseSensitiveFileNames to true, IntelliSense starts working for me :)

[jrieken]

Glad that works. We'll have to follow up with the TypeScript team. The filenames they cache shouldn't be normalised. Or they should apply the same rules then to the file paths we send them

[otbe]

Indeed 👍

[dbaeumer]

@otbe thanks a lot to track this down. Testing it on Linux would not have helped :-). I opened microsoft/TypeScript#8139 to get that fixed.

[jakepearson]

@otbe While I wait for a proper release, how do I set useCaseSensitiveFileNames? Thanks!

[otbe]

@jakepearson
Instead of hacking the source of vscode/typescript you can use a nightly build of typescript (e.g. 1.9.0-dev.20160420) and set typescript.tsdk in your user settings of vscode.

I utilize my project version of typescript for that:

"typescript.tsdk": "./node_modules/typescript/lib"

[jakepearson]

@otbe That worked. Thanks a bunch.

[arve0]

Or globally:

npm i -g typescript@next

"typescript.tsdk": "/usr/local/lib/node_modules/typescript/lib"

[dbaeumer]

This got fixed by the TS team a long time ago.