Filed, please reassign if it is filed incorrectly. https://bugs.eclipse.org/bugs/show_bug.cgi?id=497424 Patrick
From: [email protected] [mailto:[email protected]] On Behalf Of Chuong, Patrick Sent: Wednesday, July 06, 2016 4:53 PM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Debugging Javascript - No source found Our application works for nodewebkit and online. The source is the same for both online and offline, and we start the underline webserver in the nodewebkit case by using require in the index.html page load the backend javascript within the node_modules folder. The backend javascript is the main application where I want to be able to debug in the online case, which is in the node_modules folder. I’ll file a Bugzilla for this and thanks for having this fix for neon sr1. Regards, Patrick From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ilya Buziuk Sent: Wednesday, July 06, 2016 4:44 PM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Debugging Javascript - No source found Could you please create a bugzilla for allowing launch shorcuts for js files inside node_modules ? (the fix is trivial and it will heal source lookup issue for this case, but we will be able to deliver it only in Neon.1 - September 2016). Also, could you explain the reason why do you have main js file in node_modules? I'm still a bit baffled with this use-case, due to the fact that node_modules folder is typically added to .gitignore On Wed, Jul 6, 2016 at 10:21 PM, Chuong, Patrick <[email protected]<mailto:[email protected]>> wrote: I have an use case where my main application javascript file is within the node_modules folder. It is placed there for a reason and I hope I don’t have to move it outside of the node_modules folder. Yes, eclipse can find source in the node_modules if my main script is outside of the node_modules. However, if the main script is inside the node_modules, source lookup failed and breakpoint also failed. Patrick From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ilya Buziuk Sent: Wednesday, July 06, 2016 4:07 PM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Debugging Javascript - No source found Hello, Patrick I am debugging a script within the node_modules folder, and I am hitting the no source found editor. Tried adding many different source lookup container and non of them work. I also noticed the launch debug context menu is missing in the Project Explorer when right clicking on a JavaScript file in the node_modules folder. "Run As / Debug As Node.js" shortcuts were deliberately excluded from node_modules and bower_components folders for js files. Could you please explain the use-case of debugging lib / framework dependency separately from the app ? In terms of source lookup - can you debug scripts from node_modules when you start debugging on app's main js file via "Debug As Node.js Application" shortcut ? (source lookup should be tuned automatically for this case) _______________________________________________ wtp-dev mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev _______________________________________________ wtp-dev mailing list [email protected]<mailto:[email protected]> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
