You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I have seen afew issues centered around topics similar to this, but what is the official answer for disabling --debug-brk so that a breakpoint is not hit upon first run? I understand the purpose of this, in that it will allow the code to be stopped for debugging start up logic, but I am willing to live without that in order to not have a breakpoint be hit every time nodemon reloads.
Just for completeness, here is my launch.json configuration:
Sorry, the Node debugger was always breaking in a certain file at a certain place on start up. I just tested what happens if I removed that file and it fixed it. I was exporting this, which would actually run this code on start up because it was not a function that would need invoked
I have seen a few issues centered around topics similar to this, but what is the official answer for disabling
--debug-brk
so that a breakpoint is not hit upon first run? I understand the purpose of this, in that it will allow the code to be stopped for debugging start up logic, but I am willing to live without that in order to not have a breakpoint be hit every time nodemon reloads.Just for completeness, here is my
launch.json
configuration:Thanks!
The text was updated successfully, but these errors were encountered: