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.

Sign up for GitHub

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

Jump to bottom

--inspect support for source mapped files #7087

Closed
nojvek opened this issue Jun 1, 2016 · 10 comments
Closed

--inspect support for source mapped files #7087

nojvek opened this issue Jun 1, 2016 · 10 comments
Labels
feature request Issues that request new features to be added to Node.js. help wanted Issues that need assistance from volunteers or PRs that need help to proceed. inspector Issues and PRs related to the V8 inspector protocol

Comments

@nojvek
Copy link

nojvek commented Jun 1, 2016

  • Version: 7.0.0-pre
  • Platform:
  • Subsystem:

May be a devtools only change. Inspect currently does not support source mapped files.

/cc @pavelfeldman @ofrobots
@mscdex mscdex added the debugger label Jun 1, 2016
@Fishrock123 Fishrock123 changed the title ----inspect support for source mapped files --inspect support for source mapped files Jun 1, 2016
@mscdex mscdex added inspector Issues and PRs related to the V8 inspector protocol and removed debugger labels Jun 3, 2016
@ofrobots ofrobots added the feature request Issues that request new features to be added to Node.js. label Jun 7, 2016
@dmonad dmonad mentioned this issue Aug 22, 2016
Closed
@Hugheth
Copy link

Hugheth commented Nov 8, 2016

+1 is there a workaround for this?

@dmonad
Copy link

dmonad commented Nov 9, 2016

You can use any other debugger that supports source maps. VS Code works just fine for me.

@eugeneo
Copy link
Contributor

eugeneo commented Nov 9, 2016

Can you provide any details of what is not working exactly?

@canda
Copy link

canda commented Nov 30, 2016

possibly duplicate of #8369

@Trott
Copy link
Member

Trott commented Jul 15, 2017

possibly duplicate of #8369

@canda I think that one is about the legacy debugger while this one is about inspector.

@nojvek @eugeneo Should this remain open?

@Trott Trott marked this as a duplicate of #8369 Jul 15, 2017
@nojvek
Copy link
Author

nojvek commented Jul 15, 2017

The issue is that the devtools protocol which is used by inspector supports no way of loading resources.

VSCode only works if the sourcemaps are present locally, if you are debugging from remote server, then the sourcemaps reside on server, debugger (node) should be able to fetch them over network.

Chrome does this well for browser based debugging.

@eugeneo eugeneo added the help wanted Issues that need assistance from volunteers or PRs that need help to proceed. label Jul 17, 2017
@eugeneo
Copy link
Contributor

eugeneo commented Jul 17, 2017

I think this should be a help wanted issue. A way to access those source maps from a remote server needs to be designed...

@etamponi
Copy link

Hello! Any update on this? Can't node --inspect also serve the files over the websocket?

@Ralle
Copy link

Ralle commented Apr 9, 2018

+1

@refack
Copy link
Contributor

refack commented Nov 11, 2018

Put into https://github.com/nodejs/node/projects/13 backlog

@refack refack closed this as completed Nov 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Issues that request new features to be added to Node.js. help wanted Issues that need assistance from volunteers or PRs that need help to proceed. inspector Issues and PRs related to the V8 inspector protocol
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests