-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
v8::debug::GetDebugContext is going away. #18643
Labels
v8 engine
Issues and PRs related to the V8 dependency.
Comments
/cc @ofrobots |
I removed the last vestiges in core in November, see #13295. Node 10 won't be using it. I'm okay with making it inaccessible to add-ons (in node 10); otherwise it might hold us back trying to upgrade V8 mid-cycle. |
hashseed
added a commit
to hashseed/node
that referenced
this issue
Feb 9, 2018
2 tasks
hashseed
added a commit
to hashseed/node
that referenced
this issue
Feb 9, 2018
2 tasks
BridgeAR
pushed a commit
to BridgeAR/node
that referenced
this issue
Feb 10, 2018
Ref: nodejs#18643 PR-URL: nodejs#18677 Refs: nodejs#18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 21, 2018
Ref: #18643 PR-URL: #18677 Refs: #18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 21, 2018
Ref: #18643 PR-URL: #18677 Refs: #18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 21, 2018
Ref: #18643 PR-URL: #18677 Refs: #18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Feb 21, 2018
Ref: #18643 PR-URL: #18677 Refs: #18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Apr 13, 2018
Ref: #18643 PR-URL: #18677 Refs: #18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
MayaLekova
pushed a commit
to MayaLekova/node
that referenced
this issue
May 8, 2018
Ref: nodejs#18643 PR-URL: nodejs#18677 Refs: nodejs#18643 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I remember correctly we agreed on delaying the removal of
GetDebugContext
until Node 9. I would like to remove the API and more importantly the legacy code backing it. That means that Node cannot use it anymore though. It currently still does.Given the success of the DevTools protocol I think we can remove it. Can we advance this somehow so that by Node 10 it's not exposed to add-ons anymore?
The text was updated successfully, but these errors were encountered: