-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
sourcemap support for node debugger #6725
Comments
#6471 is related but is about full source map support (which is unlikely in the near future because of performance issues, but that's less of an issue for the debugger.) Can you expand on what exactly you would like the debugger to support? |
forgive my naive request - i'd like to be able to step through code with sourcemaps through the command line debugger |
Yes, everything you have in Chrome DevTools is available. |
@repenaxa ... thank you for the clarification. |
it sounds like my request is being addressed in other tickets. thank you! |
Now that we've removed the internal debugger in favor of a Inspector-based one, is this issue still reproducible? |
Closing due to inactivity. If it's still an issue please comment or (if GitHub allows you to do so) re-open. |
How can you close it as "completed"? That's total BS. If you close it as "we won't do it", that at least would make sense. The Node CLI debugger does not yet support source maps. Very disappointing. $ node --version |
i'd really like to see sourcemap support for the node debugger.
The text was updated successfully, but these errors were encountered: