-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit and continue [Node.js] #8127
Comments
No, this is not yet possible. |
@weinand thanks for your answer, but would you consider it right? 😊 |
@sant123 sure, that's the reason for the little word 'yet' 😊 |
Thanks, I really appreciate it! |
I second this, adding Edit and Continue (the ability to make changes to the Node.js source code while the debugger is in break mode) as implemented in Visual Studio will make VS Code the damned best Node.js development tool out there (not that it isn't already -- but this will definitely make a huge difference). The ability to modify your code in the middle of debugging has always been a huge time-saver for those working with Visual Studio. And the ability to modify the current executing statement (by dragging the yellow arrow in Visual Studio) is just as important. Did you know that Node.js Tools for Visual Studio already supports edit-and-continue?
I wonder how difficult it would be to get VS Code to support this as well. It seems that the Node.js debugger already supports this feature, otherwise, NTVS would not be able to implement it. Also, according to a recent Node.js survey conducted by RisingStack, the biggest pain-point in Node.js today is debugging. I think that the introduction of this feature will definitely change that, as well as mitigate the use of
Tagging @bpasero and @joaomoreno as I really think they should seriously consider and prioritize this. |
Any advance on this? Just asking 😝 |
see #6930 |
Hi, is it possible to add edit and continue in Node.js instead of using Nodemon? This feature can be appreciated in Node.js tools for visual studio.
Thanks.
The text was updated successfully, but these errors were encountered: