New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 675700 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

nodejs debugging file links dont work from console

Reported by joshung...@gmail.com, Dec 19 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2956.0 Safari/537.36

Steps to reproduce the problem:
1. git clone git@gitlab.com:joshunger/nodejsdebug-boilerplate.git
2. npm install
3. npm start
4. open URL.
5. Click on console.log file link

What is the expected behavior?
Opens file.

What went wrong?
This site can’t be reached error.  The url points to chrome-devtools://devtools/Users/junger/dev/nodejsdebug-boilerplate/index.js

Did this work before? N/A 

Chrome version: 57.0.2956.0  Channel: canary
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0
 
chrome-devtools___devtools_Users_junger_dev_nodejsdebug-boilerplate_index_js.png
120 KB View Download
step 1(b). cd nodejsdebug-boilerplate
What version of node are you using?

Comment 3 by ajha@chromium.org, Dec 20 2016

Labels: M-57
node version v6.9.1
I can't get it to work with v7.2.1.  I have another project that it works on for some reason.
Labels: TE-NeedsTriageHelp

Comment 7 by allada@chromium.org, Jan 10 2017

Cc: eostroukhov@chromium.org
Owner: l...@chromium.org
I am unable to clone the example (Permission denied (publickey).). Is this module compiled and has source maps?
Weird. No source maps. It is just a single .js file.

const koa = require('koa');
const app = koa();
const server = app.listen(() => {
  console.log('opened server on', server.address().port);
});
Cc: l...@chromium.org
Owner: eostroukhov@chromium.org
Status: Assigned (was: Unconfirmed)
I see the issue now, will investigate.
Status: WontFix (was: Assigned)
This is same issue as https://github.com/nodejs/node/issues/10338. Workaround would be to use "--inspect --debug-brk" or the recently added "--inspect-brk" flag. Please note that that bug is being looked at.

Script is retained through the reference to the callback function. Once the callback runs (and outputs the console message), the reference is cleared so the callback and all retained objects (including the script) get collected. By the time DevTools connect, VM has no knowledge about the script and cannot provide the script sources to the DevTools (by default, DevTools cannot read the local filesystem).

Sign in to add a comment