It looks like the problem with NODE_OPTIONS has been fixed, I'm not getting the Starting inspector on 127.0.0.1:9229 failed: address already in use error anymore. 🙂 However, I can't seem to get the clientside debugging working. I installed the Debugger for Chrome extension in VS Code, but I think that I miss a certain launch.json attach configuration? Excellent tutorial, thank you!
Building 🏗 https://turnshift.app, Shift Scheduling for Slack Teams.
Also:
https://nextjsnews.com
https://github.com/vvo
https://dev.to/vvo
Before: JavaScript and support
@algolia
.
It looks like the problem with NODE_OPTIONS has been fixed, I'm not getting the
Starting inspector on 127.0.0.1:9229 failed: address already in useerror anymore. 🙂 However, I can't seem to get the clientside debugging working. I installed theDebugger for Chromeextension in VS Code, but I think that I miss a certainlaunch.jsonattach configuration? Excellent tutorial, thank you!Yes you do need a launch.json configuration, and I don't think you need a particular extension on VSCode, just the regular current installation.
The launch.json configuration is inside the blog post, did you use it?
You can also first try the Google Chrome debugging method also highlighted in this blog post which requires less configuration.