![]() All your experience with debugging works here:īut I have to admit, that I don’t use the built-in NPM manager. The experience working here is like most debugging in Visual Studio. It still uses Node.exe to run the project, but running a project connects the, very good, Visual Studio debugger to the node.exe process. ![]() It even has a project type for an existing node.js project:įor me the big win here is the debugging support. Once you install the tooling, it’s as easy as creating a new project (empty or a boilerplate with Express.js). ![]() It doesn’t try to do more than it should. What I particular like is that it doesn’t change the way you use Node.js – it can live side-by-side with command-line tooling like NPM, Bower, or even node.exe. It’s been a fun course to write and one of the aspects of the course that I find interesting is that the open source Node.js Tools for Visual Studio plugin actually works really well. I’ve been working on a new course for Pluralsight on “Node.js for.
0 Comments
Leave a Reply. |