Troubleshooting
🎵Note: This documentation is outdated at this point, especially when using the Node tools in Visual Studio 2017. We're working on update docs, and will redirect you to those when they're ready.
The NTVS live diagnostics allow you to collect information about how NTVS is performing and any errors it has encountered. This is useful when reporting issues and when investigating problems.
To enable live diagnostics, open Tools -> Node.js Tools -> Diagnostic Info, and check Enable Node.js Tools Live Diagnostics output pane.
Then, during your debug sessions, output will be available in the Node.js Tools Live Diagnostics output pane
When you run into an issue, you can just copy and paste the last debug session output into a window (each debug session begins with a bunch of ------s.
- Change Intellisense levels (Tools -> Options -> Text Editor -> Node.js -> IntelliSense):
- Try switching to use ES6 Preview Intellisense in NTVS 1.2 Alpha.
- Try disabling IntelliSense
- If IntelliSense is to blame, try disabling IntelliSense for a specific package if you think that may be causing the issue. See Ignoring Directories for Analysis for full details. We recommend ignoring
- bower_components
- node_modules\core-js
- Disable ReSharper (we are working with the ReSharper team to address the memory/perf issues)
- Disable McAfee on-access scanning for your global npm directory and project directory.
- Try marking your client-side code files using the "content" build action - see Editing Client Side JavaScript from Node.js for more details
See https://github.com/Microsoft/nodejs-guidelines/blob/master/windows-environment.md#max_path-explanation-and-workarounds for details