The Java Script Intelli Sense disablement is worth noting, as the VS team starts integrating more VS Code productivity capabilities to help Java Script developers get comfortable in VS Code's environment.As explained in the October 2016 Build note, the Type Script team developed what was called an "Automated Typings Acquisition" module that "automatically installs the typings files of all dependencies in a cache on your file system" when it spots references to them in the JSON package file and some client-side libraries.It's likely that there's a bug in one of the subsiquiently referenced Java Script files.Open your JS file and once the "Updaing Java Script Intellisense" has gone from the status bar of Visual Studio (there is a menu option which will force the JS intellisense to refresh, don't remember where it is, I just created a keyboard shortcut via the Tools - Keyboard area) open up your Errors window and under the Warnings you should find the reason why the intellisense has failed to load.
I did not need to add a script reference to it on my page, it simply needed to be included in the folder structure...
For now, Java Script Intelli Sense has been disabled via recovery build 1.7.1.
But there's quite a few new and enhanced productivity and debugging features across various areas of the environment: If you do, it might introduce some confusion as to which version of VS Code is being rolled out, whether it's the September 2016 Build 1.6.1 or October Build 1.7 sans Java Script Intelli Sense.
In my case, it turns out that I was also referencing other modules from j Query UI.
Perhaps you can check that you're only importing the js files you need? A few months ago I tackled this problem and created a very basic vsdoc file for j Query UI.