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

Inspect - sources aren't visible in Node v10.9.0 #23152

Closed
ravishivt opened this issue Sep 28, 2018 · 3 comments
Closed

Inspect - sources aren't visible in Node v10.9.0 #23152

ravishivt opened this issue Sep 28, 2018 · 3 comments
Labels
inspector Issues and PRs related to the V8 inspector protocol

Comments

@ravishivt
Copy link

  • Version: v10.9.0
  • Platform: Linux backend 4.9.93-linuxkit-aufs deps: update openssl to 1.0.1j #1 SMP Wed Jun 6 16:55:56 UTC 2018 x86_64 Linux
  • Subsystem: unknown (maybe inspector?)

Upgrading from Node v10.8.0 to v10.9.0 causes a loss of visibility on generated source files in Chrome's DevTools -> Sources Tab. Chrome doesn't show any of my source files that are compiled after the debugger connects. For example, I run jest+ts-jest that compiles my tests and source files and none of these generated files are visible in chrome devtools:

node --inspect-brk=0.0.0.0:9230 node_modules/.bin/jest --no-cache --runInBand --config ./config/jest.config.js --watch

In v10.8.0:

image

In v10.9.0:

image

This issue happened specifically when upgrading from node v10.8.0 to v10.9.0. Downgrading back to v10.8.0 fixes the issues. I also verified that v10.10.0 and v10.11.0 have the same issue. I tried to find features/fixes introduced in v10.9.0 that could be related and the closest I found is #21975. Could this be the source of the problem?

@eugeneo
Copy link
Contributor

eugeneo commented Sep 28, 2018

CC @ak239

@eugeneo eugeneo added the inspector Issues and PRs related to the V8 inspector protocol label Sep 28, 2018
@Trott
Copy link
Member

Trott commented Nov 25, 2018

@ravishivt Are you experiencing this with 10.13 as well?

/ping @nodejs/v8-inspector

@apapirovski
Copy link
Contributor

Given the lack of a follow up here from the OP or anyone else, I'm going to close this out. Please feel free to reopen if this is still an issue but in that case: more info to help us reproduce and track down the bug is always appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inspector Issues and PRs related to the V8 inspector protocol
Projects
None yet
Development

No branches or pull requests

4 participants