vscode-node-debug2 | VS Code debug adapter that supports debugging Node | Code Inspection library

by microsoft TypeScript Version: v1.43.0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | vscode-node-debug2 Summary

vscode-node-debug2 is a TypeScript library typically used in Code Quality, Code Inspection, Visual Studio Code applications. vscode-node-debug2 has no bugs, it has no vulnerabilities and it has low support. However vscode-node-debug2 has a Non-SPDX License. You can download it from GitHub.

Important note: By default, this extension now delegates to the new js-debug extension which is built-in to VS Code. Please file issues on that repo. To revert to the old behavior, you can set "debug.javascript.usePreview": false in your settings.

Support

Quality

Security

License

Reuse

Support

vscode-node-debug2 has a low active ecosystem.

It has 114 star(s) with 65 fork(s). There are 35 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 205 have been closed. On average issues are closed in 582 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of vscode-node-debug2 is v1.43.0

Quality

vscode-node-debug2 has 0 bugs and 0 code smells.

Security

vscode-node-debug2 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

vscode-node-debug2 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

vscode-node-debug2 has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

vscode-node-debug2 releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vscode-node-debug2

Get all kandi verified functions for this library.

vscode-node-debug2 Key Features

No Key Features are available at this moment for vscode-node-debug2.

vscode-node-debug2 Examples and Code Snippets

No Code Snippets are available at this moment for vscode-node-debug2.

Community Discussions

Trending Discussions on vscode-node-debug2

Visual Studio Node.js Express 4 Application Server Quits

QUESTION

Visual Studio Node.js Express 4 Application Server Quits

Asked 2019-Jun-14 at 13:35

Googling didn't get me vary far with this so I wanted to make a post about it.

In Visual Studio 2017 if you create a new Node.js Express 4 Application project, build it and debug it then the Node.js server will just crash and exit before you can read any output from the CMD window that it was running in.

Checking the log file C:\Users\matt\AppData\Local\Temp\vscode-node-debug2.txt yielded no usable information for me. What was causing it to crash and how can it be fixed?

...

ANSWER

Answered 2019-Jun-14 at 13:35

First, be sure you update your npm packages in Visual Studio by performing the following steps.

In solution explorer, expand the npm node.
Right click and choose the appropriate option.
a. Install Missing npm Packages
b. Update npm Packages

That didn't fix the issue but it doesn't hurt. Now if you rebuild your project and debug it by pressing ctrl + F5 then it will pause on the error that is causing the Node.js server to crash.

So, The server is having trouble binding to port 1337. I'm assuming that's because it's such a low port number and we're running Visual Studio as a regular user and not as an administrator. To change the port number to a higher value you can edit the app.js file in Visual Studio.

I Changed the following line

to

Now, if you save everything, rebuild the project and debug it by clicking the debug button or pressing F5 the server will successfully start. The browser will still be directed to port 1337 instead of port 65073 though. After changing the port number in the address in the browser the page loads fine.

I'm not sure how make it open to the port we set. I'll update this post if I figure that part out.

Source https://stackoverflow.com/questions/56599321

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install vscode-node-debug2

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: