[1.4.2] While debugging server, node-inspector debug console is unusable

[brucejo75]

EDIT by @abernix: This is a node-inspector bug see this workaround provided by @AronVanAmmers below!.

This is new with 1.4.2: I am seeing this error when loading a server debug session

Network.loadResourceForFrontend failed.
Error: ENOENT: no such file or directory, open 'E:\mroot\meris\.meteor\local\build\programs\server\profile.js.map'

I do not know if it is related, but any commands in the console get lost in space (I assume the debugger may be parsing the entire symbol tree looking for things?). The console is unusable.

This may be related to #7977

Environment

Windows 10: 1511 (OS Build 10586.633)
Meteor: 1.4.2
Chrome: 54.0.2840.71

[akodate]

I am also getting this exact same error after the 1.4.2 update.

[aaroncalderon]

I am experiencing the same issue.

Environment

Windows 7
Meteor: 1.4.2
Chrome: 54.0.2840.71

[benjamn]

What "debug console" are you talking about? Do you mean meteor shell or meteor debug or something else? I'm confused about why you'd be using Chrome to debug server code.

[aaroncalderon]

@benjamn I believe he is refering to using meteor debug and then opening the http://localhost:8080/debug?port=5656. Then once chrome loads the page the above mentioned error happens and the console is unusable.

That is what happens to me.

[brucejo75]

Sorry. I am using node-inspector which pops up a chrome window.

This error shows up in the console window of Node-inspector:

Network.loadResourceForFrontend failed.
Error: ENOENT: no such file or directory, open 'E:\mroot\meris\.meteor\local\build\programs\server\profile.js.map'

And the console is unusable. If I type in a variable to inspect it simply does not work. This is impacting debugging fairly significantly.

[brucejo75]

@benjaminn: Does profile.js need to be in this list?

[benjamn]

@brucejo75 it gets written just above that list (builder.write("profile.js", ...))

[benjamn]

For what it's worth, we are using the latest version of https://www.npmjs.com/package/node-inspector (0.12.8).

[brucejo75]

Yeah, I upgraded everything. But the console is still dead.

Any idea why Node-inspector is looking for the map of profile.js? Does not seem to need or complain about lack of maps for any other .js files in that directory: .meteor\local\build\programs\server

[brucejo75]

I just installed 1.4.2.1 and verified the issue is still there in that version.

Repro

1. meteor create test
2. cd test; meteor
3. Bring up node-inspector

Result

• Error message on console:

Network.loadResourceForFrontend failed.
Error: ENOENT: no such file or directory, open 'E:\mroot\meris\.meteor\local\build\programs\server\profile.js.map'

• node-inspector console is not responsive to commands

[brucejo75]

OK, I found this: node-inspector/node-inspector#903

Seems that node-inspector is having a sync problem with Chrome and this bug cropped up with new versions of Chrome. Not related to Meteor...

Closing, sorry for the distraction.