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

  • Top 3 Blazor Extensions for Visual Studio Code

    Some developers prefer to create applications with Microsoft's open-source Blazor tooling from within the open-source, cross-platform Visual Studio Code editor. Here are the top tools in the VS Code Marketplace for those folk, as measured by the number of installations.

  • How to Invert a Machine Learning Matrix Using C#

    VSM Senior Technical Editor Dr. James McCaffrey, of Microsoft Research, explains why inverting a matrix -- one of the more common tasks in data science and machine learning -- is difficult and presents code that you can use as-is, or as a starting point for custom matrix inversion scenarios.

  • Microsoft Engineer: 'It's Time to Move OData to .NET 5'

    Microsoft engineer Sam Xu says "it’s time to move OData to .NET 5" and in a new blog post he shows how to do just that.

  • Microsoft Goes Virtual with Developer Education in Face of COVID-19

    Like many organizations that host developer educational events, Microsoft has gone virtual amid shelter-in-place directives and a surge in remote work stemming from the COVID-19 pandemic.

  • Microsoft Enhances Low-Code Power Apps

    Microsoft's nod to the low-code movement, Power Apps, has been enhanced with a bevy of new features, including mixed reality, canvas/model support in a new mobile app, UX improvements and more.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events