![node js tools for visual studio 2013 node js tools for visual studio 2013](https://www.red-gate.com/simple-talk/wp-content/uploads/2013/11/NewProjFromExistingCode_thumb.png)
Turn on compiling files that are not part of a project and use commonjs code generation since we are using Node.
#Node js tools for visual studio 2013 install#
Install TypeScript for Visual Studio if you dont have it installed.
![node js tools for visual studio 2013 node js tools for visual studio 2013](http://www.manfredkipfelsberger.de/wp-content/uploads/2014/12/Create_a_new_blank_azure_nodejs_web_app.png)
(I have NTVS and WebEssentials installed - some operations take a long long time, but I attribute this to NTVS being still an early version.) After installing the Node.js Tools for Visual Studio, just create a project for the JavaScript template 'Blank Node.js Console Application'.
![node js tools for visual studio 2013 node js tools for visual studio 2013](https://bitstobrowser.files.wordpress.com/2014/12/vs2013-up-and-running1.jpg)
When I press F5 (debug) I get the console.log messages I have put into the My node app actually is a REST webservice, so I want to test different URLs with different parameters.Īlso, I cannot access the app on the port I specified, though when I directly start it from node.exe I can, even though the command prompt is still open. QUnit to JsTestDriver Adapter - Translates QUnit API to JS Test Driver. JSTD (JS Test Driver) - Console Runner (Java). Sinon Adapter for QUnit - Seamless Sinon.JS integration for QUnit. I used NTVS new project->from existing sources and all files were imported successfully.Īfterwards, I opened the project settings of my project and set the node.exe arguments to bin\www, startup file for express. Eventually I came up with the combination of the tools listed below: QUnit - Unit Testing Library. I have moved an existing node.js + express project to VS because I prefer the IDE over JetBrains for now (used VS for years, only peeked into Webstorm).