开发环境使用nodemon --inspect启动多个项目 node 调试 多个

Debugging Guide

This guide will help you get started debugging your Node.js apps and scripts.

Enable Inspector

When started with the --inspect switch, a Node.js process listens for a debugging client. By default, it will listen at host and port 127.0.0.1:9229. Each process is also assigned a unique UUID.

Inspector clients must know and specify host address, port, and UUID to connect. A full URL will look something like ws://127.0.0.1:9229/0f2c936f-b1cd-4ac9-aab3-f63b0f33d55e.

Node.js will also start listening for debugging messages if it receives a SIGUSR1 signal. (SIGUSR1 is not available on Windows.) In Node.js 7 and earlier, this activates the legacy Debugger API. In Node.js 8 and later, it will activate the Inspector API.

---

Security Implications

Since the debugger has full access to the Node.js execution environment, a malicious actor able to connect to this port may be able to execute arbitrary code on behalf of the Node.js process. It is important to understand the security implications of exposing the debugger port on public and private networks.

Exposing the debug port publicly is unsafe

If the debugger is bound to a public IP address, or to 0.0.0.0, any clients that can reach your IP address will be able to connect to the debugger without any restriction and will be able to run arbitrary code.

By default node --inspect binds to 127.0.0.1. You explicitly need to provide a public IP address or 0.0.0.0, etc., if you intend to allow external connections to the debugger. Doing so may expose you to a potentially significant security threat. We suggest you ensure appropriate firewalls and access controls in place to prevent a security exposure.

See the section on 'Enabling remote debugging scenarios' on some advice on how to safely allow remote debugger clients to connect.

调试指南
本指南将帮助您开始调试节点。js应用程序和脚本。
启用检查器
当使用--inspect开关启动时，它是一个节点。js进程侦听调试客户端。默认情况下，它将侦听主机和端口127.0.0.1:9229。每个进程还被分配了一个唯一的UUID。
检查器客户端必须知道并指定要连接的主机地址、端口和UUID。完整的URL类似于ws://127.0.0.1:9229/0f2c936f-b1cd-4ac9-aab3-f63b0f33d55e。
节点。如果js接收到SIGUSR1信号，它还将开始监听调试消息。（SIGUSR1在Windows上不可用。）在节点中。js 7和更早版本，这将激活旧版调试器API。在节点中。js 8和更高版本，它将激活Inspector API。
安全影响
因为调试器对节点具有完全访问权限。js执行环境中，能够连接到此端口的恶意参与者可能能够代表节点执行任意代码。js流程。了解在公共和专用网络上公开调试器端口的安全含义很重要。
公开调试端口是不安全的
如果调试器绑定到公共IP地址，或绑定到0.0.0.0，则任何可以访问您的IP地址的客户端都可以无限制地连接到调试器，并且可以运行任意代码。
默认情况下，node--inspect绑定到127.0.0.1。如果您打算允许外部连接到调试器，则明确需要提供公共IP地址或0.0.0.0等。这样做可能会使您面临潜在的重大安全威胁。我们建议您确保适当的防火墙和访问控制到位，以防止安全暴露。
有关如何安全地允许远程调试器客户端连接的一些建议，请参阅“启用远程调试方案”部分。

---

nodemon 报错：Starting inspector on 127.0.0.1:9229 failed: address already in use

解决方案：

启动时设置 --inspect-port

  "scripts": {
    "dev1": "cross-env PORT=81 NODE_ENV=development nodemon --inspect --inspect-port=8888 app.js"
  },

在chrome输入链接：

chrome://inspect/#devices

不显示--inspect-port=8888对应的调试入口

解决方案：

 

 

 https://nodejs.org/en/docs/guides/debugging-getting-started/