Visual Studio Code 1.7.2 Replugs JavaScript IntelliSense Module

The Automated Typings Acquisition module that was disabled in VS Code 1.7 looks to be working as originally intended, and is now in a new incremental build available this week.

Remember that minor debacle last month, when Visual Studio Code October Build was rolled back to version 1.6? The issues have been ironed out and Build 1.7.2 is now available.

At issue was some JavaScript IntelliSense capabilities the VS Code team added to the original version 1.7 to help JavaScript developers automate the installation of typing files. Most of the automation comes in the form of an Automated Typings Acquisition module that was developed by the TypeScript team. When the ATA module is deployed through a TypeScript language server, it watches for package.json files to install the needed typings files based on the dependencies cached in a file system. Whether a project.json file exists, the ATA module will figure out the dependencies.

Soon after Visual Studio Code 1.7 was released with the ATA module on November 2, npm's servers were hit by what appeared to be a DDoS attack. In actuality, the rollback incident report posted on the VS Code blog noted that it was really coming from "a huge spike in registry activity from clients attempting to access non-existent packages under the @types scope."

The VS Code team immediately withdrew version 1.7 and had users roll back to version 1.6 (September Build), then to an incremental version 1.7.1 that had the ATA module disabled, but had other newer features enabled in the 1.7 release.

As of this week, version 1.7.2 with the ATA module enabled has been released. It also includes a number fixes.

On a side note, the Visual Studio Code blog has a nifty post for developers who want to contribute source code formatters to the VS Gallery for use with VS Code.

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

comments powered by Disqus


  • Vendors Update Controls for .NET Core 3.1, Blazor

    This week saw two third-party vendors of dev tools -- UX and UI toolkits and controls -- release new offerings that include support for two of Microsoft's main open source frameworks, the cross-platform .NET Core 3.1 and Blazor, which allows for creating browser-based web applications with C# instead of JavaScript.

  • C++ Is Focus of New Visual Studio 2019 v16.7 Preview 2

    C++ development is a focus point of the new Visual Studio 2019 v16.7 Preview 2, featuring a slew of tweaks and improvements touching upon remote SSH connections, IntelliSense support and more.

  • Clustering Non-Numeric Data Using C#

    Clustering non-numeric -- or categorial -- data is surprisingly difficult, but it's explained here by resident data scientist Dr. James McCaffrey of Microsoft Research, who provides all the code you need for a complete system using an algorithm based on a metric called category utility (CU), a measure how much information you gain by clustering.

  • So What's Up with Microsoft's (and Everyone Else's) Love of Rust?

    Microsoft already stewards several popular programming languages -- C#, TypeScript, F# -- so what's up with its love of Rust, along with the rest of the world?

  • C# Steps Up Programming Language Popularity Ladder

    Microsoft's C# programming language climbed a year-over-year notch on the TIOBE Index, which measures popularity among developers.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events