Remember this npm script runs Webpack in watch mode and will watch for any changes in your Sass files and output the processed CSS file. There are more VScode hints and information in the VSCode section of this site. Right click dev -> Bindings -> Projec t Open Visual Studio will run this task when you open the project. I seriously wish that I’d got this working before because it is massively useful whether you are creating your own nodes or trying to track down performance or resource issues in your flows. When the execution hits a breakpoint, you will see the current call stack, variables and more. Now you can set breakpoints by clicking to the left of the line numbers. To debug your own (or someone else’s) node, expand the “Loaded Scripts” list in the sidebar, find the appropriate script file, click on it to open. Having chosen, the debugger may pause things, if so, click on the continue icon or press F5.
All Node.js based processes will be listed. Start up Node-RED then click on the green “start debugging” icon in VSCode, you will get a popup to choose the active process you want to debug.
vscode.Īdd the following configuration to the. Open the ~/.node-red ( userDir) folder, click on the debugging sidebar and click on the cog icon which creates and opens a new file called launch.json in a folder called. Since VS Code is built on Node.JS as is Node-RED, you can also use it to debug Node-RED issues. When using Visual Studio Code, the free code editor and Integrated Development Environment (IDE) from Microsoft to develop new nodes, it has an excellent built-in debugger.
Originally from a thread in the Node-RED Google Group.
0 kommentar(er)
