


Previously, you could author IntelliSense extensions which would allow you to add custom completion results for 3rd party libraries. VSDoc is no longer supported in favor of JSDoc which is easier to write and the accepted standard for extensions XML documentation comments, sometimes referred to as VSDocs, could previously be used to decorate your source code with additional data that would be used to buff up IntelliSense results. Going forward you no longer need to think about reference management and so you don't need triple slash references comments or _references.js files.


Sometimes it was desirable to have all your files in scope, other times it wasn't, but this lead to complex configurations involving manual reference management. Previously it was fairly complicated to understand at any given moment which files were in your IntelliSense scope. intellisense.js extensions, and limited IntelliSense for specific code patterns. The most notable of these changes are the replacement of VSDoc with JSDoc, the removal of custom. ** * ) Notable Changes from VS 2015Īs Salsa is a completely new language service, there are a few behaviors that will be different or absent from the previous experience. Luckily, it is usually fairly easy to deduce a type given the surrounding code context.įor a variable or property, the type is typically the type of the value used to initialize it or the most recent value assignment. In JavaScript, most of the time there is no explicit type information available. IntelliSense based on TypeScript Declaration Files.TypeScript uses several sources to build up this information. This new information is provided by the TypeScript language service, which uses static analysis behind the scenes to better understand your code. JavaScript IntelliSense in Visual Studio 2017 will now display a lot more information on parameter and member lists. Automatic acquisition of type definitions.What's New in the JavaScript language service in Visual Studio 2017 See the VS Code docs for more info.įor more information about the general IntelliSense functionality of Visual Studio, see Using IntelliSense. The new editing experience also mostly applies in VS Code. Details are included here in this topic, and you might also want to read this blog post. The JavaScript language service in Visual Studio 2017 uses a new engine for the language service (former code name "Salsa"). Powered by a TypeScript based language service, Visual Studio delivers richer IntelliSense, support for modern JavaScript features, and improved productivity features such as Go to Definition, refactoring, and more. Visual Studio 2017 provides a powerful JavaScript editing experience right out of the box.
