This article describes how to debug the EgretWing link development tool. the EgretWing link development tool debugging problem. The EgretWing compiler supports three debugging modes: Node. js, Chrome, and EgretWing extension development.
A tool configuration error occurs during development.
In this case, you need to reconfigure the tool path in the configuration file launch. json in EgretWing.
After the project is created, configure debug information in launch. json in the. wing folder.
For example:
{"Version": "0.2.0", "deployments": [{"name": "Wing built-in player debugging", "type": "chrome", "request ": "launch", "file": "index.html", "runtimeExecutable": "$ {execPath}", "useBuildInServer": true, "sourceMaps": true, "webRoot ": "$ {workspaceRoot}", "preLaunchTask": "build", "port": 5610 },{ "name": "debug with Chrome on the local machine", "type ": "chrome", "request": "launch", "file": "index.html", "runtimeExecutable": "/Applications/Google Chrome. app/Contents/MacOS/Google Chrome "," useBuildInServer ": true," sourceMaps ": true," webRoot ":" $ {workspaceRoot} "," preLaunchTask ": "build", "port": 5610 },{ "name": "append to Chrome process", "type": "chrome", "request": "attach ", "port": 9222, "webRoot": "$ {workspaceRoot}"}]}
Click debug as follows:
The above is a detailed explanation of the debugging problem of the EgretWing link development tool. For more information, see other related articles on php Chinese network!