Node js tools for visual studio 2013
The most notable contribution is the NPM support which is a pretty significant feature from RedGate.īecause it uses the built-in JavaScript editor, NTVS requires Visual Studio Professional or higher. We reached out to them before the release, gave them access to the code, and were excited to accept their contributions. While working on it we saw several disjoint efforts to produce Node.js support for VS including RedGate's Visual Node and another "NTVS" made by some individuals. But we've also been collaborating with others before the release. I work at Microsoft on NTVS and it is built primarily by Microsoft. A Reddit user by the name of dinov explains, The figure below shows that a sample profiling report after running the app with profiler tool. The profiler can run from selecting Launch Node.js profiling from the Analyse menu of Visual Studio. So when the PTVS team at Microsoft realized what was happening they decided to solicit contributions. Another cool feature of Node.js Tools for Visual Studio, is the Node.js profiler which can be used for profiling your Node.js apps. Furthermore, they were largely based on Python Tools for Visual Studio (PTVS). The reason so many third parties are showing up is that multiple projects to support Node.js were started at roughly the same time. Bart Read from Red Gate provided the UI for this feature. Package management is handled via NPM, also known as Node Packaged Modules.
Much of the debugger work comes from Dmitry Tretyakov of Clickberry.
In the case of remote debugging, MacOS and Linux are also supported. NTVS, short for Node.js Tools for Visual Studio, offers Node.js developers a fully featured IDE complete with Intellisense, package management, profiling, and debugging.ĭebugging support is offered both locally and remotely.