This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 251779 - Debugging only in project sources
Summary: Debugging only in project sources
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Node.js Debugger (show other bugs)
Version: 8.1
Hardware: PC Linux
: P2 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-12 14:27 UTC by Vladimir Riha
Modified: 2015-04-12 18:03 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2015-04-12 14:27:40 UTC
Please consider following setup:
 - nodejs project with sources set to folder X, site root to sibling folder Y
 - node_modules folder is sibling folder to X (so it is not visible in Projects view and it is not part of project's sources)
 - start NodeJS debugging, set breakpoint to some asynchronous code
 - try to use Step Out

Very often, the asynchronous code (Promise, DB query...) uses some 3rd party NodeJS module placed in node_modules folder and as a result, the stepping out very often stops in some nodejs module and much less often in project's actual sources. 

Would it be possible to limit JS breakpoints just to project's sources? So in setup above, debugger would not stop in node_modules. If node_modules would be inside folder X, it would stop there. Or at least make it optional via some settings. 

Quite often I just want to step out to my own code and I'm not interested in 3rd party module


Thanks
Comment 1 Martin Entlicher 2015-04-12 18:03:59 UTC
That would require some smart-stepping functionality, like the one in Java debugger. And some configuration possibility. Either in Sources window or in Options...