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
For quite some time the VS Code node debugger supported a 'restart' attribute on 'attach' configurations. See https://code.visualstudio.com/docs/editor/node-debugging#_attaching-to-nodejs for details.
With this release we now support the 'restart' attribute on 'launch' configurations as well.
If this feature is enabled, VS Code will restart a debug session whenever it detects the termination of node.js.
An example for how to verify this feature uses nodemon and the following test program app.js:
In your launch config you can use Intellisense snippets to create a 'Nodemon setup' launch config.
After launching this you can edit app.js and VS Code should restart the debug session automatically.
Try to verify another scenario that uses 'restart' in a 'launch' configuration.
The text was updated successfully, but these errors were encountered:
Test for #17381:
Complexity: 2
For quite some time the VS Code node debugger supported a 'restart' attribute on 'attach' configurations. See https://code.visualstudio.com/docs/editor/node-debugging#_attaching-to-nodejs for details.
With this release we now support the 'restart' attribute on 'launch' configurations as well.
If this feature is enabled, VS Code will restart a debug session whenever it detects the termination of node.js.
An example for how to verify this feature uses nodemon and the following test program
app.js
:In your launch config you can use Intellisense snippets to create a 'Nodemon setup' launch config.
After launching this you can edit
app.js
and VS Code should restart the debug session automatically.Try to verify another scenario that uses 'restart' in a 'launch' configuration.
The text was updated successfully, but these errors were encountered: