Debugging instructions, replica WIT-DEBUG directory, StarlingMonkey debugger extension #9
Conversation
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
|
@yoshuawuyts @tschneidereit please have a look and let me know if it works for you when you have a moment. |
|
Oh, and @andreiltd thanks a ton for your work and help here. |
|
NOTE: as the current version on which this was written has now been published, caveats in the original commit note no longer apply. |
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.
This attempts to add debugging tools and instructions to the example repository using the StarlingMonkey vscode debugger (the .vsix format should work in other versions of similar tools as well).
There are several weaknesses to this PR, one of which is that the vscode debugger has been merged and smoothed out quite a bit but has not been published to the marketplace; this can be rectified easily, but I did NOT add instructions on how to build and install from .vsix.
As a result, if you use the marketplace version you may have a different experience. The awkwardness, in addition, of having to add an entire directory that is a copy of the release directory of deps is quite strange indeed, and I think something that componentize-js can think about changing. (This is now moot: #9 (comment))