This project is read-only.

1.0 Beta 2

Rating:        Based on 11 ratings
Reviewed:  11 reviews
Downloads: 17384
Change Set: 20060f086c09
Released: Jul 22, 2014
Updated: Sep 27, 2014 by mousetraps
Dev status: Beta Help Icon

Recommended Download

Application NTVS 1.0 Beta 2 VS 2013.msi
application, 3148K, uploaded Jul 22, 2014 - 14986 downloads

Other Available Downloads

Application NTVS 1.0 Beta 2 VS 2012.msi
application, 3152K, uploaded Jul 22, 2014 - 2398 downloads

Release Notes

We’re pleased to announce the release of Node.js Tools for Visual Studio 1.0 Beta 2.

Node.js Tools for Visual Studio (NTVS) is an open-source plug-in for Visual Studio which supports developing applications for Node.js written in JavaScript. NTVS supports a broad range of features including editing, IntelliSense, debugging including edit and continue and cross platform debugging, profiling, NPM integration, TypeScript, and an integrated REPL window. NTVS also makes it easy to quickly create web sites and deploy them to Microsoft Azure Web Sites or Cloud Services.

NTVS 1.0 Beta 2 is available for:
  • Visual Studio 2013 Express for Web (requires Update 2)
  • Visual Studio 2013 Pro or higher (requires Update 2)
  • Visual Studio 2012 Pro or higher (requires Update 4)

Changes since 1.0 Beta

New analysis/IntelliSense engine

This is one of the most significant changes since beta and we are interested in hearing all of your feedback. The new analysis engine should do a better job of providing completions in larger projects and should be faster to provide those completions. The new analysis engine also brings with it new features including find all references, goto definition and IntelliSense in the REPL window. We’ve also lost some features such as brace completion and outlining but those are planned to reappear in Beta 3.

Because this is a huge change we are eagerly awaiting your feedback – both positive and negative. If you run into issues with IntelliSense: that could include large memory usage or a spike in CPU usage on project load. The analysis is cached with your project so subsequent project loads should not have the same CPU impact. You can change the aggressiveness of it or disable it completely in Tools->Options->Text Editor->Node.js->IntelliSense. We’ll use this feedback to drive improvements into our Beta 3 release.

Improved NPM UI

The NPM management UI has been significantly updated to be easier to use. We’ve also added integrated support for invoking NPM inside of the REPL window with a new .npm command.

Mocha Unit Test Support

Unit test support has been expanded to add support for unit tests written using Mocha. It’s also now possible to add support for your own unit test frameworks by writing a single Node module which finds and runs the tests.

Numerous bug fixes

All across the product numerous issues have been fixed – including code formatting which was re-written for improved performance, various fixes in the debugger, improvements to project load time and more. We’d like to thank all of the people who have reported issues fixed in this release including andydots, crlf0710, Deandob, delfinof, dtretyakov, EdvinV, f0xza, flyfj, gtk2k, JamesBlunt, johnny_k, jtwillig, kgolding, kubal5003, leonzhuang, magicdawn, monkeybrother, nabog, pcttechnical, rdd3, ronba, Roquqkie, ryancrawcour, SebastienSAIGO, shacal, vernerrs.

Help Make NTVS Better

NTVS is an open source project and we’re always willing to take high quality contributions. If you’d like to contribute please check out our issue tracker for outstanding bugs and features which can be implemented. You can also help make NTVS better by reporting issues or helping out your fellow users on our forums. We’d like to thank the users who have contributed to this release by submitting pull requests including BartRead, dtretyakov and WangYugang.

Reviews for this release

Thanks for the NodeJS tools. I have been using the alpha release successfully since it has been release. Unfortunately, the beta releases have not worked out. When I open my solution file (98 projects - one is NodeJS project) with Beta 2 installed, the memory use just explodes until the VS2012 becomes unusable. I had to uninstall and re-install the alpha release.
by aboteler on Jul 31, 2014 at 3:11 PM
I've already submitted an issue regarding aboteler's problem (issue #1248). I was unable to share my project because it's company confidential (maybe aboteler can share his?). But it does seem to be due to large projects. I think the project files are getting traversed in an endless loop because VS2013 will eventually run out of memory and crash.
by u84six on Jul 31, 2014 at 9:29 PM
It could be that analysis is having problems with your project. Could you try changing the analysis level in Tools->Options->Text Editor->Node.js->Intellisense and re-opening your project? You could 1st try the medium setting to see if that works better or try turning it off if it's still problematic but you'd like access to other features like debugging. We are continuing to fix performance issues w/ the analysis engine for the next release.
Reply by dinov (N/A) on Jul 31, 2014 at 10:50 PM
Thanks to NTVS I can happily use VS to work on my Node projects written in Typescript and debug in Typescript right inside VS. There are still a few stability issues to work out but I rarely experience them.
by stkb on Sep 25, 2014 at 11:28 AM
The js editor has no outlining at all, while editing js in a MVC project does. Is there a way to enable outlining?
by leoxy520 on Sep 15, 2014 at 8:04 PM
With the Visual Studio 2013 version I cannot create a project, it always says, "Illegal character in path" how can I fix it? The fix is, install god damn node.js :D I am sorry guys :/
by Knerd on Sep 10, 2014 at 1:33 PM
Not a big fan of the new, faster and (unfortunately) semi-crippled intellisense engine. Paren and brace matching, snippets, VSDOC comments, and more are all borked for me. Bummer.
by bbroome on Sep 3, 2014 at 5:03 AM
Can you provide some additional details about what issues you're having with intellisense? Are there places where you're not getting completions but expecting them?
Reply by dinov (N/A) on Sep 2, 2014 at 9:00 PM
I'm using NTVS since alpha 1 and thanks for this great plugin that transforms Visual Studio in a Node JS IDE. But I use a yoga i5 with 8GB of RAM and I see that the latest version "Beta 2 released in 7/22" gets a huge use of CPU with just a solution of NodeJS open.
by aadanelon on Aug 26, 2014 at 4:10 PM
TL;DR: Set Tools > Options > Text Editor > Node.JS > IntelliSense to "No IntelliSense". It will still work, but you won't have CPU/memory problems. Works fine. Using default settings, my VS2013 keeps using 1-3 cores (variable), while increasingly using more memory (>1.8GB when I shut it down). As suggested by @dinov, I tried lowering the Intellisense levels to Quick IntelliSense (no change in memory/cpu usage) and No IntelliSense (CPU usage stopped, memory remained the same). After restarting VS2013 with the "No IntelliSense" setting, and waiting until CPU usage 'settled', it used ~450MB. No more CPU burning. And despite the name of the setting, it seems that IntelliSense still works! Tried Rename, code completion, parameter completion, Find all references, all looking good. After running an "npm update", I did get a lot of lines like "Failed to push new glyph for C:\Source\foo\node_modules\bower\node_modules\bower-config\node_modules\optimist\node_modules\minimist\example\parse.js. Return code from SccGlyphChanged was -2147024809." in my "Source Control - Git" output window when a code-completion popup is shown. Also, VS still seems to indent 'try/catch' blocks the wrong way
by MPoelstra on Aug 1, 2014 at 2:38 PM
Astounding progress. Considering that this is still a beta, things look great for the final release. Well done.
by poseidonCore on Jul 25, 2014 at 9:51 AM
First of all, well done on beta 2. From a quick test on a large project I do not seem to be experiencing slow saving issues as from previous releases. The intellisense has not crashed but has stopped giving parameter hints. I also noticed my custom snippets are not available in the JS editor when I start typing the shortcut for inserting any snippet.
by jquest on Jul 22, 2014 at 10:56 PM
thx jquest - not using JSLS anymore and doing another intellisense engine means we had give some things we got for free (eg brace matching). they'll be implemented soon. i've opened a new issue for custom snippets.
Reply by Ptools (N/A) on Jul 23, 2014 at 5:49 AM
Thanks for fixing the test debugger. Works for TypeScript files as well. Great work so far!
by nabog on Jul 22, 2014 at 7:34 PM
thanks nabog! please let us know how intellisense does for you pls.
Reply by Ptools (N/A) on Jul 22, 2014 at 10:22 PM