News

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

Featured

  • Microsoft Highlights Visual Studio Live! Event Lineup and Longtime Developer Community Role

    A Microsoft MVP Blog post on Visual Studio Live!'s longevity arrives as the 2026 conference series continues with upcoming stops at Microsoft HQ, San Diego and Orlando.

  • Using Local AI to Cut Copilot Usage-Based Billing Shock

    After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.

  • .NET 11 Preview 5 Focuses on Performance, Productivity and Safer Code

    .NET 11 Preview 5 focuses on under-the-hood runtime performance gains, streamlined APIs and language features that reduce boilerplate, plus built‑in security checks and incremental ASP.NET Core and EF Core improvements aimed at everyday developer productivity.

  • VS Code 1.124 Focuses on Agent Autonomy and Parallel Sessions

    Microsoft's June 2026 VS Code update turns on Autopilot by default and adds background sending for agent sessions.

Subscribe on YouTube