I've included additional details here microsoft/vscode-recipes#52
I assume a property would need to be added to the node launch config to allow this to work correctly, and that this property doesn't already exit.
I did attempt to use restart: true, but that didn't correct anything.
- VSCode Version: 1.91.1
- OS Version: 10.12.6
Steps to Reproduce:
- Clone the sample project
git clone https://github.com/SteelPhase/vscode-meteor-test vscode-meteor-test
- CD into the directory
cd vscode-meteor-test
- install npm dependencies
meteor npm install
- open vscode without extentions
code --disable-extensions .
- launch
Meteor: Node launch config
- wait util meteor launch, and debugger attaches
- modify
!! Change me !! on line 6 of server/main.js to any value
- save file
- wait for
=> Server modified -- restarting...
- debugger will disconnect, and in doing so kills the npm, and meteor node processes
Expected end result:
Meteor should restart as usual with the file change, and either the node debugger should detach, or reattach as the debugger becomes available again.
Reproduces without extensions: Yes
I've included additional details here microsoft/vscode-recipes#52
I assume a property would need to be added to the node launch config to allow this to work correctly, and that this property doesn't already exit.
I did attempt to use
restart: true, but that didn't correct anything.Steps to Reproduce:
git clone https://github.com/SteelPhase/vscode-meteor-test vscode-meteor-testcd vscode-meteor-testmeteor npm installcode --disable-extensions .Meteor: Nodelaunch config!! Change me !!on line 6 of server/main.js to any value=> Server modified -- restarting...Expected end result:
Meteor should restart as usual with the file change, and either the node debugger should detach, or reattach as the debugger becomes available again.
Reproduces without extensions: Yes