You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inspect - sources aren't visible in Node v10.9.0 #23152
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:
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?
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.
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 --watchIn v10.8.0:
In v10.9.0:
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?