update debugging instructions#1221
Merged
dherault merged 1 commit intodherault:masterfrom Apr 13, 2022
Merged
Conversation
|
Someone should get this merged, good documentation. |
Owner
|
Love it @Bilal-S , thanks, I remember you from way back, you're the first maintainer of this package <3 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I had written the debugging instructions when we were still using node 4.x (4 years ago). They needed updating.
Motivation and Context
I needed to update the debugging instructions. There was no clear guide for this that I could find via a brief Google search so an update was needed to save people headaches.
How Has This Been Tested?
I use those debugging settings actively for my environment with latest version of VS Code (1.55.2)
I tested this with plain Javascript and Typescript + webpack.
For both variations I am able to open an interactive debugging session with full call stack and variables being available.
Screenshots (if appropriate):