Fix unclickable triangles in node-inspector#565
Open
dpolivy wants to merge 1 commit intotjanczuk:masterfrom
Open
Fix unclickable triangles in node-inspector#565dpolivy wants to merge 1 commit intotjanczuk:masterfrom
dpolivy wants to merge 1 commit intotjanczuk:masterfrom
Conversation
The version of node-inspector being used is very old, and contains some calls which no longer work in Chrome. node-inspector itself fixed this bug in December of 2014, and it's frustrating enough for me that I ported the changes into iisnode's version of the debugger. Original fix: node-inspector/node-inspector#479
Contributor
Author
|
@rramachand21 I can't be the only one running into the issue of not being able to expand variables with node-inspector on Chrome; it'd be awesome if you could look into pulling this fix into a future iisnode release! |
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
1 participant
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.
The version of node-inspector being used is very old, and contains some
calls which no longer work in Chrome. node-inspector itself fixed this
bug in December of 2014, and it's frustrating enough for me that I
ported the changes into iisnode's version of the debugger.
Original fix: node-inspector/node-inspector#479