intellisense not working for Javascript files stored in sharepoint document library

[Wayne-Shen]

• VSCode Version:1.5.2
• OS Version:Windows 10

Steps to Reproduce:

1. Upload a JavaScript to a SharePoint document library
2. Open the document library within windows explorer
3. Open the Javascript file with VSCode

4. Javascript intellisense is not working
5. the file path is "\servername@portnumber\DavWWWRoot\siteurl\documentlibraryurl\folder\test.js"

Please help to look at this issue, thank you!

[chrmarti]

Are you getting IntelliSense when typing Math.? Could you paste the content of test.js?

[Wayne-Shen]

nothing was show whatever I typed，console. Math. function even var. VSCode
behaves like notepad

2016年9月22日 上午12:04，"chrmarti" notifications@github.com写道：

Are you getting IntelliSense when typing Math.? Could you paste the
content of test.js?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#12350 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADIYUIuN1N2mWP5rR3tYFBtlQDEi3CtHks5qsVV2gaJpZM4KCXSR
.

[chrmarti]

What is the detected language shown in the lower right corner of the window?

[chrmarti]

@waderyan Any idea why a file on a SharePoint would not have IntelliSense? (I tried with a network path and that worked fine.)

[waderyan]

This may be related to microsoft/TypeScript#10735

@Wayne-Shen can you do the following to help us debug the issue?

Set this flag in your settings. Then open the Output window. Send us a screen capture.

"typescript.tsserver.trace": "verbose"

[Wayne-Shen]

Hello @waderyan ,

I followed your steps and find the error message is:

TypeScript Service: tried to cancel request with sequence number 2. But request got already delivered.
TypeScript Service: canceled request with sequence number 3
TypeScript Service: canceled request with sequence number 5
TypeScript Service: canceled request with sequence number 8
...

[waderyan]

Ok thank you. This is the same thing we have seen before in this issue microsoft/TypeScript#10735