FAQ

FAQ

Why am I getting errors when running my node project in VS that do not occur when running from the command line?

It is possible that nodejstools is using a different copy/version of node.js to the command line. Check the project properties "node.exe path" and modify if necessary. For example nodejstools may default to "C:\Program Files (x86)\nodejs\node.exe" when you have installed a 64 bit version in "C:\Program Files\nodejs\node.exe".

How does Nodejstools depend on Nodejs and npm versions?

For basic editing node and npm do not need to be installed. You will be warned if you use a feature requiring either and they cannot be found (they are searched for in project settings and then the environment) Otherwise, intellisense does not depend on node version but only installed modules can be analysed. The latest versions of node have been tested for breaking changes as described in the manual test matrix.

Can I use multiple versions of node and switch between them?

Yes. Use a node version manager such as nvm-windows. You can also specify the node location in the project settings.

What dependencies does using nodejstools introduce to my code?

Almost none. Apart from the usual Visual Studio solution and project files, which you'll probably want to add to version control, other files are generated when required. In fact, the import existing code option means the solution and project files can also be generated on demand. Otherwise, nodejstool simply uses your existing files and command line tools.

Why are the my editor settings such as use spaces for tabs not being followed?

nodejs has it's own setting in the editor language options and does not use the javascript settings.

What `.gitignore` file should I use?

You can use this VisualStudio file that will cause git to ignore `node_modules` and nodejstools temporary files. You might also like to include this node.js file as well.