Skip to content
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

vs code debugging issue #658

Closed
tanekim88 opened this issue Aug 5, 2018 · 2 comments
Closed

vs code debugging issue #658

tanekim88 opened this issue Aug 5, 2018 · 2 comments

Comments

@tanekim88
Copy link

tanekim88 commented Aug 5, 2018

Issue :

VS Code's DEBUG CONSOLE's variable lookup doesn't work.
To reproduce: Just create a simple typescript file, set breakpoint, and hit breakpoint, and try to read any local variables that were set. But when I tested just now, it won't even hit a breakpoint. So there are 2 issues. 1.it won't hit breakpoint. 2. Even if it hit a breakpoint, you can't read any loacal variables that were set.
But it works well in version 22 though. Version 23 is the problem

For more detail,
I uploaded a repo:
https://github.com/tanekim77/ts-jest-not-working
To test, please install vs-code extension called "Jest",
and reload.
Then, goto aa.test.ts
After a while, you will see "Debug" button magically appear above test(..).
If not, restart vs code and you will see.
sset a breakpoint. and press debug.
It won't even hit a breakpoint.
downgrade to v22, then it will hit a breakpoint, and will be able to read local variables.

Expected behavior :

variable lookup should work.

Output from debug log :

# content of debug.txt :

Minimal repo :

@huafu
Copy link
Collaborator

huafu commented Aug 5, 2018

Interesting issue 🤣 If it's about debugging, I think this ...will... be a duplicate of #627.

If it is the case, simply close this issue, else edit your description to provide more details please 😉

@huafu
Copy link
Collaborator

huafu commented Aug 5, 2018

Thanks @tanekim77 for the update.
I'm closing this since with your update it looks like a duplicate of #627, which I'm taking care of now. Please subscribe to the updates on the that issue instead.

@huafu huafu closed this as completed Aug 5, 2018
@huafu huafu added the duplicate label Aug 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants