-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
[email protected] fails to build #14411
Comments
Note that there are no issues on 8.1.4. Any Ideas on where to begin? |
Reported at node-inspector/v8-debug#43 as well (please always cross-link issues if you’re opening multiple ones).
That sounds odd; the Also, it looks like this has been fixed in recent versions of v8-debug. |
Can you try clearing your global npm modules? |
How do I do that? also for some reason |
@PCGeekBrain Looks like That that API is going away is not under our direct control; it’s something that’s happening upstream in V8 and that we basically just have to accept as a breaking change that comes with Node 8. Also, the entirety of V8’s Debug API is being deprecated and will be removed in Node 9 or Node 10 (again, outside of our control), so it’s probably a good idea to move away from I’m closing this as it’s not an issue with Node itself, just a breaking change that happened and that we can’t really revisit, sorry. Keep node-inspector/v8-debug#43 open and try to find a solution there on the module’s issue tracker, but right now v8-debug just isn’t working with Node 8. |
v8 commit log related to this issue
|
Here is a full log of the issue.
sudo
andnvm
both have not been able to get around it.The text was updated successfully, but these errors were encountered: