Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Debuging es6 Proxy as property -> Internal error: illegal access #12749
Steps to Reproduce:
1 - If I, in node.js 6.6, write (resp. have transpiled from TypeScript) a class like that:
2 - And then instantiate it like this:
3 - When I debug in Visual Studio Code and I want to watch the var table I always have
written there, meaning I can not watch table or any of its properties.
The same thing works perfectly fine in Chrome.
I have raised this on Stackoverflow:
But should I anyway be able to debugg Proxy objects run in node.js in vscode? Because in fact at lest in my case it does not seam to work... when I create a Proxy object as var and not as property I do not see any variables under 'Variables' in the Debugger view at all and when I add one to the watch I see same message on it 'illegal access'.
Btw.: node.js Version 6.7.0
This node crash occurs when retrieving the stack trace through the v8 debugger protocol:
There is nothing I can do about this (and node-inspector shows exactly the same behaviour).
The debug code there is deprecated so it's pretty unlikely to be fixed (and that's why these issues pop up with new JS features). I recommend using
This was referenced
Dec 8, 2016
added a commit
Dec 8, 2016
referenced this issue
Dec 12, 2016
@pannous You could try to use this approach: https://code.visualstudio.com/updates/v1_9#_user-level-launchjson
In the next release we will pick the correct debugger automatically.